Remove treble clef from Custom Key Signatures Creator
Reported version
3.6
Type
Graphical (UI)
Frequency
Few
Severity
S5 - Suggestion
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
In Master palete -> Key Signatures -> Create Key Signature
there is a treble cleff, which has no music function "Note: The treble clef is only decorative - custom key signatures for any type of staff can be created here." and is only confusing many users.
It would be better, to remove this "decorative" cleff from there, until transpositions for custom key signatures will be added (if ever it is plan, to do that).
Fix version
4.0.0
Comments
Interesting suggestion! I like it, although of course, better if we can make it so you actually can design a key signature that is clef-aware.
In reply to (No subject) by Jojo-Schmitz
I would say many, because (almost) every forum question about Custom Key signatures is "why it doesnt adapt clef" and answer is (almost) everytime "clef is only decorative", which in other words means "treble clef shouldnt be there".
Came up again in https://musescore.org/en/node/320132 (and before in #317526: Bug when creating custom key signature and #316951: Custom key signature function only displays an array of accidentals but not the stave intended for creating the key signature
Given that most complaints about custom key signatures have to do with them not adapting to clefs, and given that this is by design, I would suggest that a better solution might be not to remove the clef but to allow multiple clefs. So under the staff you would have a button "Add clef" which would open a menu of clefs, the selected one then being added to a new stave under the existing one(s), where you can then define the version for that clef.. (Presumably musescore already has some internal provision for per-clef definition of the standard key signatures, on which the custom signatures could piggy-back.)
Should I file a new feature request for this idea, or would that only add to the confusion?
Have you tested on MuseScore 4? Much improvement has already been made, with more changes pending. Best to be sure to explore what's already in the works, and then make suggestions for further refinement from there is still necessary.
Looked at latest nightly build. Suggest closing this and related issues with fixed in 4.0
Done 😉
Automatically closed -- issue fixed for 2 weeks with no activity.