Key command question - Graphic Editor

marquito · Post by **marquito** » Tue Apr 25, 2017 1:39 pm

Just upgraded to DP 9.13 and noticing some strangeness with certain key commands...

In earlier versions of DP when in the Graphic (MIDI) Editor hitting TAB would advance the selection from one note to the next note on the grid (or list) and Option-Tab would select the previous note. It was a quick way to get around and select events. The commands are called either Next or Previous List Element in the Commands Window.

In 9.13 however hitting TAB opens up the field to edit the grid resolution in the top right corner of the window instead. Option-Tab still selects the Previous event as expected.

So I go to the Commands window and see that TAB is assigned correctly to 'Next' and verified that it's not assigned anywhere else in case there was a conflict. The Previous command meanwhile has nothing assigned in the Commands window but for some reason still responds to the Option-Tab command.

However, when I try to assign a different key to the 'Next List Element' it still won't respond - no matter what key command I assign to it.

So, it would appear that the 'Next List Element' command is not working or is somehow disabled and also that the TAB key has been mysteriously 'hardwired' to open up the Grid Resolution field.

Can anyone else reproduce or verify this behaviour or am I missing something obvious?

Thanks for any help!

reedster · Post by **reedster** » Tue Apr 25, 2017 3:32 pm

Move Selection to Next Event is the command associated with Tab in Commands window that "advances the selection from one note to the next note"

Over here the Tab key does as you described. All Controls setting may be the issue: http://osxdaily.com/2010/02/26/use-the- ... -mac-os-x/

Assigning "Move Selection to Next Event" to a MIDI event or a different key combination does get the command working. Tested with shortcut Shift Control Option Command Tab.

marquito · Post by **marquito** » Tue Apr 25, 2017 6:14 pm

Well spotted!

'All Controls' was indeed the reason for the default Tab command no longer working like it used to - the OS now seems to prioritise its use within DP for text boxes and data entry etc. I hadn't noticed it before and wonder when that became the case... Yosemite, Sierra?

I had also forgotten the exact name of the key command which added to my confusion.

Anyhow, I've now got the command working again by reassigning it to a different key combination.

Thanks so much for the reply!

dogeatdogg · Post by **dogeatdogg** » Thu May 11, 2017 10:42 am

I just assigned different key commands and it is now working.
Thank you

FMiguelez · Post by **FMiguelez** » Thu May 11, 2017 1:05 pm

reedster wrote: Over here the Tab key does as you described. All Controls setting may be the issue: http://osxdaily.com/2010/02/26/use-the- ... -mac-os-x/

Assigning "Move Selection to Next Event" to a MIDI event or a different key combination does get the command working. Tested with shortcut Shift Control Option Command Tab.

Now I got it working and I see how it's useful.

Thank you for the tip, reedster

Michael Canavan · Post by **Michael Canavan** » Thu May 11, 2017 2:50 pm

marquito wrote: So, it would appear that the 'Next List Element' command is not working or is somehow disabled and also that the TAB key has been mysteriously 'hardwired' to open up the Grid Resolution field.

Hey this is obviously a bug, repeatable and not what we or MOTU want. We should all report it.

stubbsonic · Post by **stubbsonic** » Thu May 11, 2017 4:40 pm

Michael Canavan wrote:
marquito wrote: So, it would appear that the 'Next List Element' command is not working or is somehow disabled and also that the TAB key has been mysteriously 'hardwired' to open up the Grid Resolution field.
Hey this is obviously a bug, repeatable and not what we or MOTU want. We should all report it.

But to be clear, is a selected note in the MIDI graphic editor considered to be a "List Element"? In other words, does the "Next List Element" command not work when it is an actual list (like a chunk in the chunk list, or a note in the event list, etc.)?

Michael Canavan · Post by **Michael Canavan** » Thu May 11, 2017 11:07 pm

stubbsonic wrote: But to be clear, is a selected note in the MIDI graphic editor considered to be a "List Element"? In other words, does the "Next List Element" command not work when it is an actual list (like a chunk in the chunk list, or a note in the event list, etc.)?

On my system at least, and I suspect it's true for all of us it's Move Selection to Next Event that's assigned to the Tab key command, the Option Tab key command Move Selection to Previous Event works as expected in the Graphic Editor as described by marqito, and the Tab key command jumps to edit the grid resolution instead of (on my system at least) doing what it's assigned to which is Move Selection to Next Event.

I wish the Commands window had a simple "search for key command" as in jotting in Option Tab would bring up any key commands assigned to that function, but the work around is easy, just fake assign an empty key command slot in the Commands window and DP will tell you what commands are assigned to that key command and ask you if you want to assign anyway.

philbrown · Post by **philbrown** » Fri May 12, 2017 3:19 am

Michael Canavan wrote:
stubbsonic wrote: I wish the Commands window had a simple "search for key command" as in jotting in Option Tab would bring up any key commands assigned to that function, but the work around is easy, just fake assign an empty key command slot in the Commands window and DP will tell you what commands are assigned to that key command and ask you if you want to assign anyway.

Just thinking the same thing last week. Why the search command ignores key commands doesn't make any sense to me. A semi-automatic way to "Disable Other Key Commands" would be nice too, instead of having to hunt down the other assignments and delete them manually.

stubbsonic · Post by **stubbsonic** » Fri May 12, 2017 7:40 am

On a related note, I'd sure like a little legend saying what all those key symbols are.

frankf · Post by **frankf** » Tue May 16, 2017 5:39 am

Copy/paste the table in this URL (http://www.osxkeyboardshortcuts.com/key ... mbols.html) into a text or word or whatever file (or add the URL itself), and add the text file it URL to a DP global clipping called Help or similar. Optionally: Put the open Help Clipping somewhere on your screen in your templates and re save them. Tip: Put PDF manuals for plug ins, effects, hardware or any other work related files you may need access to while in DP. You can leave the actual files where they live and put its alias in the Help clippings folder.

To find if keystrokes are used in DP I type them into an empty slot in the Commands window as mentioned. A dialogue will pop up if there's a conflict and show the conflict(s). BUT, you have to search manually for keystrokes assigned in System Preference>Keyboard. I've never seen a way to list those but maybe a script is out there. BTW, if you use Keyboard Maestro and assign Global shortcuts there you can also run into conflicts. True for any background utility that let's you assign a global keystroke to a function.

stubbsonic · Post by **stubbsonic** » Tue May 16, 2017 7:40 am

That's a great idea. I haven't fully embraced clippings in my workflow, but this is yet another very clever and HELPful (pun intended?) tip. I just downloaded that PDF. THANKS!!

MOTUnation.com