Measure Number behave strangely when inserting Section break onto Horizontal Frame
Reported version
3.4
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
closed
Regression
Yes
Workaround
Yes
Project
OS: macOS High Sierra (10.13),
Arch.: x86_64, MuseScore version (64-bit): 3.5.0.27580,
revision: b5add95
It happens also in v3.4.2
Step to reproduce: (see attached file)
1.Insert horizontal Frame (Add->Frames->Insert Horizontal Frame)
2.Put Section break onto the Horizontal Frame
3.Input the note in second or later measures in second system
Result:
Measure number on beginning of the second system is changed from 1 to 5
*Section break Inspector, “Start new section with measure number one” is being ticked while this processing.. umm strange.
Workaround: (measure number changed from 5 to 1)
Just save the file or ticking this “Start new section with measure number one” off and on again
Attachment | Size |
---|---|
measure_number.mscz | 3.13 KB |
Fix version
3.6.0
Comments
Confirmed.
3.Input the note in second or later measures in second system
Actually any non-1st measure of that non-1st section
And any measure of any subsequent measure
Or just save the file.
In reply to (No subject) by Jojo-Schmitz
It works fine in v 2.3.2.. (open attached file in v 2.x)
Bug also present in 3.2.3 and 3.1
In reply to Bug also present in 3.2.3… by Jojo-Schmitz
One more workaround I've found :
just drag the measure number :)
or Doubleclick, Esc
In reply to or Doubleclick, Esc by Jojo-Schmitz
Hi jojo!
Double click, esc the measure number? nothing happens to me..
Relates also to #295629: Horizontal frames interrupt section break formatting and to #288098: Long instrument names appear in first system after vertical frame. Our code dealing with combinations of section breaks and frames is not very robust. I have a fix (maybe) for those other two issues, but measure number calculation happens elsewhere, I'll see if the same basic fix will work there (probably it will).
https://github.com/musescore/MuseScore/pull/7026
The pull request has been merged.
Automatically closed -- issue fixed for 2 weeks with no activity.