Next System Shortcut

• Aug 25, 2019 - 13:03
Reported version
S5 - Suggestion
PR created

As with the shortcut to "go to next measure", it would be nice to also have "go to next/previous system" as a shortcut. Something like, instead of Ctrl+R/L, Shift+Ctrl+R/L to do so would seem naturally related to "go to next measure".


In reply to by mike320

Sorry, I get it now.

For example, you edit the notes of an instrument and want to move to the next system and stay on the same instrument.

If there is not a very large orchestral score, Alt + Up/Down Arrows will still work if there are 3/5 instruments (just a few more clicks required).

If they define a shortcut : This only works in Page-View. It will generate an error in Continuous-View (because there is only one system here).

In reply to by Ziya Mete Demircan

It need not generate an error. As a matter of fact, it would make functional sense to keep the same shortcut to be an alternative function for continuous view.

Something like: If in page view: "go to beginning of next system". If in continuous view, go to beginning of the measure after the next page break/section break, and if there aren't any, then get information of 'next system' by what is available in page view based on current score settings, and then go to the beginning of said measure. Or something like that. It would be useful and speed up score traversal.

In reply to by Ziya Mete Demircan

Another observation:
if the user has selection somewhere in the second or third measure of a system, the ["Previous"] function of this request would not go to the previous system first but to the beginning of that system containing those measures. And then, if pressed again, it would go to the first measure of the previous system, selecting the first duration element (note/rest). ["Next"], however, would take the user to the beginning of the next system and not the "end" of that system they're in.

Again, these two commands would be very useful in page view. In continuous view, again, follow the system breaks and if there aren't any, then either do nothing (probably a safe bet ;) or let these functions also double as "go to beginning of score and select first duration" / "go to score's last measure's first element". Something along those lines.

In reply to by worldwideweary

Not much enthusiasm expressed about the idea of next/prev system shortcuts, eh?

After looking into continuous view, I noticed that no matter what, systems aren't taken into account. Whether or not there are system breaks, a [Select All Similar] with the [System] checked won't result in only that system being selected. It's as if, while in continuous view, there is absolutely no concept of systems implemented, even with the very existence of system breaks visually seen while in continuous view.

Because of this, I don't feel obliged to think that the future implementer, ahem (might have to do this myself), would have to get it to work with these shortcuts either, meaning that either these would do absolutely nothing while in continuous view, or end up being like some alternative such that [previous system] would go to the absolute beginning of the score with its first chord/rest element selected, and [next system] taking the user to the last measure of the score while in continuous view. I suppose it could be useful for that purpose.

Status active PR created

Stuck with functionality of traversing systems and not traversing individual instruments while using these. I'd be willing to change that if people brought some conversation, but for now in my opinion this will be more useful (for me at least). Meaning, the next command will take the user to the top-left beginning of the next system, and the previous command will take the ussr to the top-left beginning of the current system if selection position is in the middle of the system somewhere, or even in the beginning but not at the topmost staff, and then this will take the user to the top-left beginning of the previous system when used again.

In reply to by worldwideweary

In doing this, I also came across what I consider to be a bug:

While in note-entry mode, if the user is in voice-two for instance, using the "go to next measure" command will lose which voice the user is in and go directly into voice-one upon the next measure, even if there are second-voiced notes in the next measure!

When I was going to implement keeping track of the current voice (before choosing to stay with going to the top-beginning of a system for entry), I had forgotten to check this and realized that the regular [next/prev measure] command doesn't do it either, so let the idea go.

...Actually this could more than likely be fixed easily, so it might be something up for modifying in the future if people wanted it. It seems logical to do so in my opinion. The voice is kept correctly using the regular left/right arrows, but not with next/prev measure commands.