Accessibility: navigation in voices, notes vs. rests ?

• Dec 17, 2017 - 17:16
Reported version
2.1
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

In recent weeks, I've been using the accessibility feature to help me for enter fingerings in a multi-voices context. It's really helpful for me.

I read the part in the handbook about accessibility: https://musescore.org/en/handbook/accessibility#scorewindow
There is, however, something that I am not sure if it is an issue, or if it is the intended behavior and implemented as well. And if that's the expected behavior, I don't understand the reason and the consistency.

To sum up, when you navigate with the shortcut Ctrl + Alt + Shift (to go to the next element), the navigation is performed as expected with the notes in the four different voices, Voice 1 -> Voice 4

But when there are rests instead of notes, the same shortcut "forgets" the note of the lower voice and immediately switches to the next beat /next measure.

You can go back with the reverse shortcut, or use Alt + Up / Down, but it's disturbing, this breaks the workflow (it's not always easy to anticipate ). And again, I do not understand the consistency of the behavior between the notes and the rests with this shortcut.

In attachment, see a test file that summarizes this behavior in the various scenarios. Thanks for explanation, and confirm or not if it's the intended behavior: voices rests accessibility.mscz

Comments

• Dec 17, 2017 - 18:03

Looks like a bug indeed, thanks for reporting!

FWIW, a future version will have a different algorithm used by default, one that actually moves through all elements, not just a handful. For instance, it will also navigate through fingerings, accidentals, etc. The old command will also be provided for compatibility. Its use in entering fingerings was not really considered in this. You might want to check out the nightly build of master and try out the two different versions of the command (you might need to set up a shortcut for the new one) and discuss your impressions in the forum.

Reply

• Dec 17, 2017 - 18:23

Okay, thanks for confirm this issue (I was not sure because the accessibility was an area completely unknow for me)
Of course, I will check with a nigthlty build of master. I was not aware of the different algorithm you talk about, and the moment when that it was implemented. Thanks.

Reply