Measure Numbers gone wild

• Dec 6, 2018 - 21:49
Reported version
3.0
Priority
P0 - Critical
Type
Graphical (UI)
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
MuseScore

I set a negative offset to a measure number. Then I added a crescendo in a measure after the measure with the newly set number. As an effect, the measure numbers started to show a wrong count, decreasing further every time the crescendo is changed. If the complete view is updated, the numbers will show a correct count again. Switching the focus away from MuseScore and back to it again is enough to fix the view.
I added an example that shows the buggy numbers.

Attachment Size
BuggyUI.PNG 38.38 KB
NonBuggyUI.PNG 45.78 KB
sample.mscz 9.37 KB

Comments

• Dec 7, 2018 - 04:20
Priority ⇒ P0 - Critical

Wow, crazy! Indeed, load the score attached to the original post, double click the crescendo, and start editing - dragging, left/right, shift+left/right, whatever. Or adjust any setting in Inspector. As you do, watch the measure number at beginning of the system go wild!

Reply

• Dec 7, 2018 - 10:15

Also when I repitch some note in the first system in the sample score (not every though) the measure number offset seems to get forgotten, and that measure number always shows 7.

Reply