Unable to add mid-measure clef on the first tick of a measure
Reported version
3.0
Priority
P1 - High
Type
Functional
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project
MuseScore has supported mid-measure clefs on the first tick of a measure for a while, but in the master branch, the ability to create them has been lost. When dropping a clef onto the first ChordRest in a measure, the clef is supposed to be inserted right before the ChordRest, in the same measure. Instead, it is moved to the end of the previous measure.
I suspect that this a result of commit 9f12f2aa7c to fix #139316: Regression: inability to change a clef inside a system leads to crash. Werner has confirmed that it is indeed a bug.
Fix version
3.0.3
Comments
See fix #272887: Unable to add mid-measure clef on the first tick of a measure #3694.
Came up again in #279272: Mid-measure clef cannot be entered on first beat of measure.
Sheesh, I swear I looked first. Glad it's already got a PR - thanks, Matt!
Fixed in branch master, commit 6df5c1c9aa
Fix #272887: Unable to add mid-measure clef on the first tick of a measure
Fixed in branch master, commit bab29bf4e9
_Merge pull request #3694 from mattmcclinch/272887-midmeasure-clef
fix #272887: Unable to add mid-measure clef on the first tick of a measure_
Fixed in branch 3.0.x, commit fb1137d1bc
_Merge pull request #3694 from mattmcclinch/272887-midmeasure-clef
fix #272887: Unable to add mid-measure clef on the first tick of a measure_
Automatically closed -- issue fixed for 2 weeks with no activity.