Option for how snap view or jumping works
Not sure if this has already been discussed. What I know is that when inputting notes or selecting notes, the view of the page suddenly shifts.
For this, my problem is when I'm inputting notes onto a staff, MuseScore automatically assumes that I'm done inserting notes and shifts to the next empty staff. (I'm using Continuous View.) I then have to drag the page back, insert another note, and then it happens again and I'm still not done.
I made a video showing what happens for those who are confused: https://youtu.be/w66wELV3c6Y
My request is that I would like an option in Preferences > Note Input that allows us to turn this on/off. I also think this idea would apply to playback view if you want to consider it.
Comments
I would very much support this option if it included a way to navigate through a page using the keyboard rather than moving only to the top of the page.
I notice the (Shift) or (Ctrl) or (Alt) plus arrow keys seem to be unused when no element is selected on the score.
In reply to I would very much support by xavierjazz
Probably Ctrl or Shift since those are rather close to the arrows and makes it possible to press with one hand. Alt is a little more of a stretch.
Can you post the specific score you are having trouble with and precise steps to reproduce the problem? In general, what you are showing shouldn't happen, and I can't reproduce that behavior on my system. The measure in which you are entering notes is supposed to stay in view - that's the whole point.
BTW, are you aware of the more efficient note input methods, such as simply *typing* the notes? Way way way way faster than all that clicking. There is also the Piano Keyboard window, also the option of using MIDI input. See the Handbook section on "Note input" for more information.
In reply to Can you post the specific by Marc Sabatella
I find this happens often, especially when I am working in the last bar of a page or the last bar of what is on screen. I don't use continuous view.
In reply to I find this happens often, by xavierjazz
Well, it is definitely to be expected that after entering the *last* note of a measure, the cursor will move forward to the next measure, and because the cursor has moved forward, the view will move with it so that the cursor remains in view. But the video appears to show something else - the view was being shifted such that the cursor was *not* in view.
Basically, since MuseScore is trying to make sure the cursor remains in view, what would be needed would be an option to *not* advance the cursor after entering a note. I'm not sure anyone would actually like that in practice - you'd constantly be having to advance the cursor manually.