Scrolling among staves with keyboard shortcut
Reported version
3.2
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
No
Workaround
Yes
Project
0) Open the attached score.
1) Select with the mouse the silence on the lower staff of the first measure.
2) Press the keyboard shortcut to "go to higher pitched note on chord".
The first silence on the upper staff is selected, but the one that was previously selected still is, you end up with both of them selected instead of scrolling.
Notice that if notes (as opposed to silences) are involved, as on the second measure, then the keyboard shortcut works as one would expect.
| Attachment | Size |
|---|---|
| Untitled.mscz | 6.9 KB |
Fix version
3.3.0
Comments
Actually, the bottom rest is no longer selected, it just appears that way. And In other situations nothing appears to happen at all - no change in what appears on screen, but the selection really does change as evidenced by the status bar. This will be fixed by my PR https://github.com/musescore/MuseScore/pull/5221
It only looks like both rests are selected, because not enough of the window is being redrawn. But the selection only contains one element, and that is the first rest on the upper staff. The handler for "next-chord" and "prev-chord" etc. end with a call to
ScoreView::updateAll(), which simply callsQWidget::update(). The handlers for "up-chord" and "down-chord" should probably also do the same.Sorry, posts crossed.
(new PR is https://github.com/musescore/MuseScore/pull/5270)
Fixed in branch master, commit ceaea1f149
_fix #292510, fix #292928: navigation and screenreader support for frames
Added code to read the text within frames in accessibleExtraInfo(),
but also fixed the navigation to check for a frame
before moving to the next/previous measure.
Because frames will generally have a track of -1,
I also needed to take advantage of the tracking of the current track from a previous commit
so that nagivation continues on the correct track after passing through a frame.
I also needed to be careful to handle the -1._
Automatically closed -- issue fixed for 2 weeks with no activity.