Shortcut to change tabs *right to left* needed, like Ctrl+Shift+Tab

Please don't assign to yourself, unless you plan to fix it yourself too ;-)

See also #59986: [Mac] Ctrl+Tab to switch between scores does not work and #60521: Add shortcut for switching between parts in a score.

It has been over a year, what's the hold up? :-)

I changed the version to 3.0 because no version was assigned and it now requires an assignment. It also affects 2.0.

So let's hope we can fix it for 2.0.3 too

The hold up is that no one has volunteered to work on it yet.

Sounds like a no-brainer fix. If someone can point me in the right direction as to where the keyboard shortcuts are handled in MuseScore, I'll take a stab at it.

There is no one place that shortcuts are handled - it depends on the context. shortcuts.xml and shortcut.cpp set up an association between shortcuts and the commands they invoke, then the commands themselves are handled either in scoreview.cpp or cmd.cpp for the most part. However, I don't think any of that is relevant herem My understanding is that tab switching isn't handled by MuseScore at all - it's handled by Qt.

Is it possible that Qt offers further options that can be turned on?

came up again: https://musescore.org/en/node/282882

New pull request: https://github.com/musescore/MuseScore/pull/5325

For the record, it had nothing to do with Qt, we just passed in the wrong parameter to our own changeScore() function (1 instead of -1).

So it was a no-brainer fix after all, sorry I misled!

Fixed in branch master, commit c004f199fa

_fix #293229, fix #66961: incorrect screenreader feedback on score change

In AccessibleScoreView::text() where we should be returning the name of the score,
we were returning "???" with a "TODO" that shows an attempt to get the name() of the score.
It didn't work because we really need to get title().

In addition, the previous-score command was not working correctly,
instead getting the next score.
Combined with the lack of screenreader feedback
this made it difficult to track which score you are editing.
The fix was just a matter of changing "1" to "-1" in the call to changeScore()._

Fixed in branch master, commit 5fa3c1c04a

_Merge pull request #5325 from MarcSabatella/293329-read-tab

fix #293229, fix #66961: incorrect screenreader feedback on score change_

Automatically closed -- issue fixed for 2 weeks with no activity.