This is true - the value is never used in the code. To be honest, I'm not quite sure what it is supposed to do. In 2.3.2, it to set a margin before the first note for a measure in cases where the measure starts with a clef, key, or time signature. In 3.0, we now have two new setting, "System header distance" and "System header with time signature distance" that perform these functions. Maybe we should just retire "Clef/key right margin", and on import from 2.3.2, take that value and assign it to the two new properties?
Theere needs to be a control for the space after mid-measure clefs. Since the old style parameter was ignored, chances are some current scores are setting it to weird values and suddenly honoring it would be bad, so I just invented a new style setting and hooked it up to that same dialog.
Comments
This is true - the value is never used in the code. To be honest, I'm not quite sure what it is supposed to do. In 2.3.2, it to set a margin before the first note for a measure in cases where the measure starts with a clef, key, or time signature. In 3.0, we now have two new setting, "System header distance" and "System header with time signature distance" that perform these functions. Maybe we should just retire "Clef/key right margin", and on import from 2.3.2, take that value and assign it to the two new properties?
https://github.com/musescore/MuseScore/pull/5020
Theere needs to be a control for the space after mid-measure clefs. Since the old style parameter was ignored, chances are some current scores are setting it to weird values and suddenly honoring it would be bad, so I just invented a new style setting and hooked it up to that same dialog.
Fixed in branch master, commit 55cb6c5b9a
fix #285535, fix #284613: spacing of mid-measure clefs
Fixed in branch master, commit 624b90d8e0
_Merge pull request #5020 from MarcSabatella/clef-space
fix #285535, fix #284613: spacing of mid-measure clefs_
Automatically closed -- issue fixed for 2 weeks with no activity.