Add 'logical' measure number to status bar

• Dec 15, 2015 - 00:45
Type
Graphical (UI)
Severity
S5 - Suggestion
Status
closed
Regression
No
Workaround
No
Project

Posted at the suggestion of Marc Sabatella. See discussion at: https://musescore.org/en/node/90571

In brief, Musescore indicates numerically where in the score the cursor sits at any given moment. This appears in the status bar in two different places: On the left (with fuller info including note pitch, duration, voice, measure, beat, and staff) and on the right (a simple 'chronological' read-out such as 98:02:240 meaning measure, beat, and sub-division). This information can be invaluable to someone doing input for keeping track of where they are while working on two or three different keyboards simultaneously and referring to a paper part or score which may be full of erasures, crossed-out measures, and errors (especially when copying autograph manuscripts or 18th-century editions).

However, both read-outs in the status bar give the 'ABSOLUTE' measure number, and do not take into account (a) 'irregular' pick-up measures which have been set to be excluded from the measure count, or (b) section breaks, which restart the 'logical' measure numbering for subsequent movements of longer works.

As there are TWO read-outs in the status bar, I would like to request that one of them be re-configured to give the 'logical' measure number--the one which will actually appear printed in the score when it is finished. Having the 'absolute' measure number in the other read-out is important for finding one's way back into a score using CTL+F.


Comments

Now that I think about it a bit more, I think it would be better to have to 'logical' measure info in the right-side read-out, as it is simpler and less cluttered with other data.

It looks like this feature now exists, as "Displayed measure: xx" in the status bar?
But what I'd also like to be able to use Ctrl+F to jump to the next measure whose displayed number is what I type (so if I have multiple movements in a score, the first Ctrl+F to "m1" would go to the first measure of the whole piece, then if I did it again, it would go to measure 1 in the next movement etc.)

Status active fixed
Regression No
Workaround No

Let's mark this as being fixed then

Put you new request into GitHub's tracker, this one here has been discontinued