Today I upgraded to the latest version of Dorico. While working, I noticed that the return key suddenly performs different functions than usual. For example, it now jumps from line to line in the project info window instead of triggering the apply function as in former versions. In my opinion, the tab key is intended for the line jump and the duplication is unnecessary and annoying. This hinders my workflow considerably, as I hardly ever use the mouse, because there is no longer a key that triggers the apply button.
1 Like
This isn’t a new thing. I can’t tell you exactly when we made it such that Return moves to the next control in Project Info, but it’s been that way for many versions.
If you’re on Mac, with the latest version of Keyboard Maestro you can bind a hotkey (I use the “hyperkey” which is remapped Caps Lock key, with C and Q, for my left hand) to press the Apply and Close buttons without mousing around.
Because there are (at least) two kinds of “Close” and “Apply” buttons in Dorico interface, I need a simple “if then else” function in the KM macro. But this way you can greatly reduce mouse use with dialogs. (If you’re on Windows, I can’t help specifically, but I would assume AutoHotKey or some other macro software offers similar functionality.)
1 Like
Actually, I have only upgraded from version 5.0 and something … and can therefore no longer trace whether this has been the case for such a long time. I just find it inconsistent when the return key triggers “apply” in all other windows except the project window. Furthermore, I don’t understand why two keys (Tab and Return) are needed that have the exact same functionality. Perhaps the “enter” key (on the Mac) to the right of the number block could at least perform the apply function.
This could should be regarded as a wish from a keyboard aficionado like me …
Dear Robert, thank you very much for your answer. As I own Keyboard Maestro, I could actually implement your suggestion, but I’m still hoping that my wish to the team will be taken into account in an upcoming update before I throw myself into programming. But thanks again for the tip!