scope of renumbering measures
Reported version
3.0
Type
Development
Severity
S4 - Minor
Reproducibility
Always
Status
duplicate
Regression
No
Workaround
No
Project
If a bar is renumbered, item noOffset appears in xml for this bar as an offset to internal numbering.
Only the number of the selected bar is displayed correctly, all following numbering remain untouched and wrong.
After reloading, all numbering is displayed correctly.
Perhaps the best way is adding noOffset after correction to all following bars up to a bar with a special and redraw all bar numbers after correction.
In the dialog for renumbering it would be helpful to show the internal numbering and the (editable) corrected number and to
save the difference as noOffset.
Fix version
3.0.5
Comments
Sample XML file?
to save the difference as .?
See also #288968: Include both correlative and user-defined measure number in status bar
In reply to (No subject) by hbtron
sorry, the xml-items where not shown in my initial text because i did not know how to escape special chars.
I just ommitted the brackets now.
you mean
<noOffset>
?And it is not about (Music)XML but about the MuseScore mscx/mscz format, right?
In reply to you mean <noOffset>? by Jojo-Schmitz
I have just observed item 'noOffset' changing in mscx according to the dialog. Sorry, but i am not familiar with (Music)XML, so perhaps my suggestion is not applicable.
Well, you initially called it XML, which I, apparently wrongly, assumed to mean MusicXML
I can't reproduce though, ehgen I chenge measure 1's offset, the other measure numbers follow immediately
I'm using 3.2 though, that sample score had been last saved with 3.0.2, so I guess you'd need to upgrade
See #284019: measure numbers are not updated on subsequent systems after adding offset
In reply to (No subject) by Jojo-Schmitz
I will prove that as soon as 3.0.5 or 3.2.0 is available by Linux Snappy. Currently either 'sudo snap refresh --revision=3.2.0 musescore' or 'sudo snap refresh --revision=3.0.5 musescore' fails.
You can use an AppImage meanwhile
In reply to You can use an AppImage… by Jojo-Schmitz
thanks a lot ! In AppImage 3.2 renumbering of measures is correct.
Because Ticket 288968 is still active, this ticket can be closed.
No, #288968: Include both correlative and user-defined measure number in status bar is not fixed yet, and is about a different (but somewhat related) issue. Me mentioning it above was mostly misunderstanding your issue
en_US spelling ;-)