Incorrect or no navigation via keyboard if featuring grace after note

• Aug 11, 2014 - 19:09
Type
Functional
Severity
S4 - Minor
Status
closed
Project
MuseScore

1. Open attached score (produced in 2.0).

2. Click on C.
3. 'Right' (on keyboard).

Expected result: The highlight is on E.
Actual result: The highlight is on the grace after note.

4. 'Left' or 'Right'.

Result: No movement.

-----

2. Click on G.
3. 'Left'.

Expected result: The highlight is on the grace after note.
Actual result: The highlight is on E.

4. 'Left'.

Result: The highlight is on the grace after note.

5. 'Left' or 'Right'.

Result: No movement.

Using MuseScore 2.0 Nightly Build (3a4f0bc) - Mac 10.7.5.

Attachment Size
Incorrect or no navigation via keyboard if featuring grace after note.mscz 1.62 KB

Comments

• Aug 11, 2014 - 20:41

This will definitely be worth looking at as part of the accessibility work that is currently going on Anything that prevents keyboard navigation is a more serious problem for blind users than you might otherwise think.

Reply

• Aug 17, 2014 - 07:57
Status (old) active ⇒ patch (code needs review)

See https://github.com/musescore/MuseScore/pull/1148

See also #23418: Grace chords cannot be reached in Edit mode. Currently, navigation includes grace notes (poorly, as per the current issue) even when in note input mode, but note input only affects the main notes, not the grace notes - even though it may appear you have navigated to a grace note. My PR here actually makes it so that while in note input mode, grace notes are completely skipped. That seems better to me than being able to navigate to a grace note but then find that actual note entry affects only the parent note.

Reply