• Date
    John728
  • Date
  • Replies 6 replies
  • Subscribers 187 subscribers
  • Views 2121 views
  • Users 0 members are here

Feature request: 2.3 Hotkeys

There are some commands I use very frequently that are not mapped directly to any keyboard keys without modifiers. It's hard to remember which key + modifier corresponds to which command and it's a lot faster to be able to press one key rather than hold a modifier key and press another key. The Data command should definitely be its own key (without a modifier) because a lot of the time I need to hold [data] and press another key or click something.

 

There are quite a few keys on the standard U.S. keyboard that have no hotkeys assigned to them. I propose mapping them as follows:

F10          data

F11          select last

F12          go to cue

`               Undo

Scroll Lock            effect

Pause/Break          stop effect

[               +%

]               -%

Insert      Learn

End         stop/back

  • At least 4 of the above aren't available on Mac they're trying to keep things consistent across platforms and other language keyboards.
  • in reply to Nick Simmons

    The ultimate solution of course, is to allow us to map the keyboard ourselves. I've been very fond the this flexibility in Vectorworks. A default mapping would always be required, but there is much that depends on the user and their situation.

    I see this as something that might stay with a console rather than a show file. But with merging from show files that is less of an issue.

  • in reply to RickR
    don't xkeys give you enough flexibility? i mean if it's really that important...
    • At least 4 of the above aren't available on Mac they're trying to keep things consistent across platforms and other language keyboards.

      Nick

      Right, that's why they have different combinations of keys. I'm saying to not get rid of any current shortcuts so things wouldn't change for users of other keyboards.

      The ultimate solution of course, is to allow us to map the keyboard ourselves. I've been very fond the this flexibility in Vectorworks. A default mapping would always be required, but there is much that depends on the user and their situation.

      I see this as something that might stay with a console rather than a show file. But with merging from show files that is less of an issue.

      This is a good idea but only if it's possible to save keyboard layouts and switch back and forth. The reason for this is I sometimes have to cover another programmer and I would need the ability to return the keyboard layout to how it was before. I was day playing on a show recently as an electrician, so I didn't have my X-keys and I ended up running the Ion for a little while, while the programmer was in the bathroom.

  • in reply to RickR
    I like this idea, making an individual shortcut mapping will very helpful for the people who works often with OSCnomad.
  • in reply to sstaub
    With OSCnomad I don't care what the shortcut keys are..... I have the keys I want to use in my OSC layout. Since I started using Lemur over OSC to nomad I don't have to use the main computer keyboard for anything other than labeling.
Related

www.etcconnect.com