Pressing zero when not in note entry mode causes cursor to jump back several measures to random place instead of entering a rest
I switch back and forth between musescore and Transcribe doing transcriptions. Oftentimes when I switch back, if I'm not in note entry mode but a whole rest is selected, if I press 4 and then 0 thinking that I'm going to start some quarter note rests, the cursor/selected note jumps back some random amount of measures and modifies some other measure.
It seems to do this intermittently.
Windows 10 Home Dell XPS 13.
Comments
I have seen this also, but have lived with it. It seems to me that this happens when I have nothing selected when I thought I did. Pressing either 0 or a note will cause some random previous measure to be selected and if a note is pressed the randomly selected note will be changed.
ok I noticed a specific time when it does this. If I'm out of note entry mode and there is a box around the measure, and I press zero intending to make the first beat a rest, it jumps back to some random measure approx 4 measures prior to where I am. Can't figure any reason it should be doing this.
In reply to ok I noticed a specific time… by Paul McEvoy
So the first picture if it posts is of the measure I selected. The 2nd picture is what happens after. Third picture shows the measure after I press undo (showing the original measure that it jumped to)
In reply to So the first picture if it… by Paul McEvoy
Ok it won’t let me load the initial picture but it’s just a measure with a box on it. It doesn’t do it if I just select the rest but it still seems like a bug.
In order to investigate, we would need a score and precise steps to reproduce the problem.
Normally, if you have a single note or rest selected when you press any of the note shortcuts (the notes A-G or 0 for rest), that one note or rest is replaced by the note or rest you just typed the shortcut for. I can't find any sequence of events in which this doesn't happen.
If you have nothing selected, or if your selecting is anything other than a single note or rest, what happens is we try to guess where you might want to start note input, and of course we might guess wrong. Depending on the specifics, the input might start at the last note input position, or the top left hand corner of the viewable area, or the measure we can identify as being most closely connected to the selection. These behaviors were all in response to specific user requests over the years, to support various different workflows.
If you can identify a specific sequecne of events in which you can state a rule about how you'd like us to guess your intent better, feel free to start a discussion on the forum to make sure others don't have other expectations, and once a consensus is reached, we can look at implementing tweak to the algorithm,
no feedback