Clef doesn't change when adding clef to first measure of score
Reported version
3.0
Priority
P0 - Critical
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Latest master, Ubuntu 18.04 LTS.
Reproduce:
- Create a new score with any combination of instruments
- Add a clef from the palette to the first measure
Result:
although the staff is affected as though a clef has been added (i.e. pitch is different, clefs in succeeding systems are changed), the first measure's clef looks the same.
Expected result:
The first measure's clef changes to the type dropped onto it.
Bonus bug: undoing after changing the clef causes a crash (debug build)! Hence severity S2.
I'm going to investigate this, although who knows if I can fix it :)
Fix version
3.0.5
Comments
Caused by: https://github.com/musescore/MuseScore/commit/bab29bf4e919a46d07b3818f9…
https://github.com/musescore/MuseScore/pull/4690
and https://github.com/musescore/MuseScore/pull/4740 for 3.0.x
Fixed in branch master, commit 73c83c93b0
fix #284307: clef doesn't change when adding to first measure
Fixed in branch master, commit 3f9d76e1b7
_Merge pull request #4690 from jthistle/284307-clef-first-measure
fix #284307: clef doesn't change when adding to first measure_
Special fix for 3.0.x is needed, still see https://github.com/musescore/MuseScore/pull/4740.
In reply to (No subject) by Jojo-Schmitz
In addition, program crashes (ver 3.0.4) if after a clef change on first measure, I clic "Undo" command (Ctrl + Z)
Yes, this will be fixed in 3.0.5 by the PR linked above @ciospe .
Fixed in branch 3.0.5, commit b642cc8e0d
_fix #284307: clef added to first measure doesn't change
Manually apply fix from #4740_
Fixed in branch 3.0.5, commit 8e6ce90613
_Merge pull request #4690 from jthistle/284307-clef-first-measure
fix #284307: clef doesn't change when adding to first measure_
Is this related to #285605: Tenor Clef does not appear after repeat also?
Not really, although that was my first thought too :-)
Automatically closed -- issue fixed for 2 weeks with no activity.
This isn't fixed in 3.0.5 from what I can see in https://musescore.org/en/node/286937
I think it's fixed in general, but doesn't work in 3.0.5 if the score starts with an mmrest. It does work in current master, though. See also #285423: Mid-measure clef changes do break multimeasure rests, but don't show the changed clef
If it's fixed in master, then it can be closed.
But that fix had been applied to 3.0.5 too, so should be fixed there?