Trying to assign as many of my Write Mode keyboard shortcuts as possible to Preferences> Window>Switch Mode>Write. The idea is that I can then omit Command-2 to return to Write Mode by instead typing the keyboard command for the next Write Mode operation, like inputing a note, a slur, an articulation etc. which does speed things up for me. However, I find that I cannot double-assign items that are called “Edit” items. An example would be S for inputting a slur. When I try that, this comes up:
“This key sequence is already assigned to: Edit > Do you want to remove it from that command and assign it to: Window > ?”
I don’t want to remove it from its present assignment, I just want to double assign it, which is possible for keyboard commands like Shift-F, Q etc. and is working great. So I am wondering whether or not it is possible to assign Edit item key commands to multiple functions.
There’s no restriction on which commands can have shortcuts consisting of multiple keys in sequence. I suspect the issue is that the combination you’re trying to assign really is already assigned to something else, though by the looks of things Dorico isn’t quite able to tell you exactly what command it’s colliding with.
Thank you @dspreadbury Are you making a distinction between single and multiple key commands? I have successfully double-assigned the commands U and V as well as many double key commands to two functions at once, but not S.
For example Shift-M, or U will take me back to Write Mode if I am in Engrave mode and then operate normally in Write mode. The following announcement is shown during the key command assigning process for ones that I can get to work like that:
“Key sequence also assigned to another command, which will override it when its context takes precedence etc.” and I can immediately add it to the list of key commands.
But for some commands like S, the announcement says
“Key sequence already assigned to Edit>”
and if I try to add it to the list I get the warning:
“This key sequence is already assigned to: Edit >
Do you want to remove it from that command and assign it to: Window >”
This prevents me from using it for both functions since it seems to be threatening to remove it from the first function.
Not what you are asking for, but as your question hints that you work in write and engrave mode in parallel I might just say this. When I do that, I keep two windows open, one in engrave mode and one in write. Then I can quickly go from one window to the other without delay.
Thanks @LAE That was just suggested to me in another thread. However, I would need two monitors to do that, and my second monitor is used for sources. So I would need three monitors, which is tempting but probably impractical from the ergonomic point of view.
I do a lot of back and forth between the modes, since I am editing, not inputting pitches, and often forget for a moment that I am in Engrave Mode and hit a Write Mode command. Double assigning prevents this from being a waste and actually makes the process more efficient since it is quicker for me to input the same command twice than input two different commands.
Of course, I see. Some of my most used shortcuts are “E G”, “E F”, “E N” and “E S” for the four sub modes of engrave mode. I have not so far experimented with what you are trying, I will certainly do so. To start editing in write mode I often just double click a note from engrave mode, but that takes me straight into note input and I understand that this is not always what you want.
Btw, I also only have two monitors, but what I have found very productive instead of switching between windows, I am taking advantage of the multiple desktops function in Windows (something similar exists on OsX) — much more predictable and efficient.
Having used Dorico for less than a year, I am only now getting to the point where I am after more efficiency. I recently started to use the commands for the Engrave subgroups. The double clicking into Write mode is something that I sometimes do by accident, but I haven’t been using it consciously to change mode for some reason.
Thanks for the tip about the the side by side windows. Haven’t tried that yet with Dorico. Macs do have a way to do do that automatically. I used work with multiple windows one above the other in Finale, but I had to arrange those manually each time since Macs don’t have a mechanism for that.
I think there are third party apps to deal with window positioning on Mac (as on Windows) but what I was referring to here (virtual desktops) is called “spaces” in osx and is an integrated part of the OS.
Thanks again @LAE I’ll investigate “spaces” to see if that could be helpful.
I just attempted to add Shift-Z, which is my command for hiding rests, to the Key Commands>Window>Switch mode>Write list of commands and once again was not able to because of the warning that it would remove the command from its function of removing rests:
“This key sequence is already assigned to: Edit > Remove Rests
Do you want to remove it from that command and assign it to: Window > ?”
And yet I was successful in adding T (add tie) to the Key Commands>Window>Switch mode>Write list because the warning did not appear.
So I could add T (add tie) to the list but not S (add slur). I am not sure why that is.
If you are essentially trying to create multiple commands, then have you thought about recording Scripts for these sequences, which you can then trigger with fairly short key commands from the Jump bar?
If I have understood correctly, the workflow John is suggesting will make Shift+M switch to Write mode if pressed in Engrave mode. Then Shift+M will have to be pressed again to enter the Time signature popover.
@benwiggy I’m assigning Write Mode commands to also automatically switch back to Write Mode if I am in Engrave mode. (Key Commands>Window>Switch mode>Write). This is so I can go back to Engrave Mode with the same command that I am about to use in Write mode, or if I forget that I am in Engrave mode when I type a Write mode command, it will take me to Write mode automatically. This works beautifully for most of the Write mode functions, but not for all. I was inquiring as to why that was.
@LAE just explained it much more succinctly and clearly than I did.