setting top staff to small affects some texts that are attached to the system rather than the staff
Priority
P1 - High
Type
Functional
Severity
S3 - Major
Status
closed
Regression
No
Workaround
No
Project
Setting top staff to small affects some texts that are attached to the system rather than the staff, like measure numbers, tempo markings, rehearsal marks, system text, volta, repeats and jumps
Instead it should affect staff ralated things only, like instrument change and staff text
Comments
I've noticed this as well and I have not liked it.
Came up again in https://musescore.org/en/node/181546
I'll take a look...this seems like it might be easy fix.
also present on latest 3.0-dev 3543170
Interesting related glitch in 3.0-dev: #182211: Time Signature position of numerals not updated when staff size change
Came up again in https://musescore.org/en/node/232371
Probably there should be a checkbox in the text style/properties to control this, like the current "size follows staff space", because sometimes you might still want the small text, but yeah, I think this should be addressed.
I have also experienced this issue when adding an Ossia staff. The workaround I used was to manually adjust/resize all the elements of the affected part one by one (multiplying each sizing factor by 10/7 to undo the "70%" default for a "small staff"). Fortunately, my score was small.
Nevertheless, it'd be great to see a fix for this.
Came up again in https://musescore.org/en/node/280093
So, does everyone agree this is just wrong? Am preparing a fix...
https://github.com/musescore/MuseScore/pull/4710
Fixed in branch master, commit aa0c232f75
fix #171036: don't scale system elements with staff size
Fixed in branch master, commit ea56495436
_Merge pull request #4710 from MarcSabatella/171036-system-text-scale
fix #171036: don't scale system elements with staff size_
Fixed in branch 3.0.5, commit ba17ba724b
_Merge pull request #4710 from MarcSabatella/171036-system-text-scale
fix #171036: don't scale system elements with staff size_
Automatically closed -- issue fixed for 2 weeks with no activity.