Hotkeys for "move pitch down/up" and "select previous/next chord" throw you to the beginning of the score
I am using the newest version of Musescore. Whenever I press the hotkeys for moving selection down/up or selecting previous/next chord (which are by default the arrow keys), I am always moved to the beginning of the score when nothing is selected. Sometimes this might happen even if something is selected.
Often even when I have selected something and use the hotkeys, due to a misclick, lag or something there is no selection after all and boom, back to the start you go and navigation begins again.
The behaviour is incredibly frustrating and forces you to constantly navigate your way to where you were before being magically teleported to the beginning. Too much of my time with Musescore is being consumed by magical teleports and having to navigate to the original position.
The bug (or feature?) persists if the hotkey is changed, so I am betting that this is due to the part of the code that defines what happens when these particular hotkeys are used.
If this is a feature, it is an utter nuisance and perfectly redundant as there already is a hotkey for going to the beginning of the score.
Comments
I have not seen this behavior so I don't know what might be happening. Please describe exactly what shortcuts are you trying to use? Rather than saying "hotkeys for moving selection down/up" say "Alt+Shift+Up/Down Arrow" or whatever. It's not impossible that you are simply using a shortcut that has been changed.
In reply to I have not seen this… by TheHutch
I had the actions bound to the arrow keys (which is by default), and I did try changing them to all sorts of keys such as home key, insert, F1-F12 etc. but the behaviour persists. I also tried binding the actions to compound hotkeys such as Ctrl + Left Arrow. I made sure that there are no other actions bound to these keys. Resetting all of the shortcuts to their defaults also does not fix the problem.
Currently the cursor keys do indeed get mapped to the "home" operation when nothing is selected. There has been some discussion about this and some work done to provide more sensible behavior when you press a cursor key with nothing selected - see https://github.com/musescore/MuseScore/pull/24157. Seems the work is stalled, but anyhow, it does seem to be on the radar. Since this work is not connected to any specific issue, I'd recommend you open one, at https://github.com/musescore/MuseScore/issues, and reference the exist PR from the previous link.
In reply to Currently the cursor keys do… by Marc Sabatella
Very interesting. I was actually thinking of trying to alter the source code myself to change this behaviour, but I have no prior experience with developing Musescore. I will probably do as you recommend, maybe even try fixing the behaviour myself.