This corner of the app could do with some TLC
[EDITED: - user error here ] Firstly, although Dorico will give a detailed warning of clashes and priorities for key commands, it doesn’t for Jump Bar Aliases. Nor does assigning a Jump Bar Alias overwrite a previous assignment. So you can assign b for Beam Together, simultaneously with Accelerando (Three Lines). Depending on what you’ve been ‘jumping to’, jb will invoke one or other of the assigned commands.
You also can’t determine what a particular alias might do from the Preferences/Keyboard Shortcuts pane. As with the Jump Bar, you don’t get a warning of a clash if you make the assignment here, nor can you search for an alias, and the Print Summary webpage does not show Jump Bar Aliases.
In this scenario, the only way to find out why feathered beams are sometimes appearing is to delete your Beam Together alias, go back to the jump bar, hit b and see what pops up.
There are other inconsistencies between Jump Bar Alias management and Key Command management:
Search: the Jump Bar’s search is ‘fuzzier’ - better. If for some reason you want to create a diagnostic report but can’t quite remember the command, searching create report in the Jump Bar will find what you want
Not in the Key Commands pane though, you have to type at least create di. Not good.
Then there’s a difference in how the assignments are displayed. In the pane below, the jump bar alias is actually shift-b. If you just type b you’ll see a lower case b. Conversely, if you type a lower case b into the key command pane at the top, you will see an upper case B
And finally for now - what is the point of those ‘submenus’ under key commands in the left hand pane? They don’t do anything except scroll in the event that your pane is unworkably small. You would stretch the pane or scroll with the mouse before clicking here.
