Expose default staff in editstaff.ui

• Apr 26, 2017 - 22:16
Reported version
S5 - Suggestion

When I submitted a fix for #4954: Change instrument via staff properties doesn't affect clef, I mentioned making this feature request to expose the default clef to editstaff.ui, for instance in a QComboBox like:


That value would be updated when the user changes the instrument, but also the user would be able to manually directly set the default clef with that QComboBox (which might be desired if the user wants to the keep the same sound and transposition of current instrument, but merely wants to change the default clef).


To me, this really becomes valuable when you can then save the result to a personal instruments.xml file for future re-use. Also change the other staff attributes, like transposition, range, MIDI sound, etc. I'm not saying that without all that other stuff the feature is useless, but maybe give some thought to how it could be expanded to allow for that in a way that feels like a natural extension of what you start out with.

That is a good point. I could imagine the "Edit Staff/Part Properties" dialog (editstaff.ui) be extended a bit with some more instrument-specific configs like you mentioned, and then also include a "Save to Custom Instrument" button which would save all those instrument-specific things the a personal instruments.xml.

It might make sense to hide all these extra details under a [+] expansion button so that this editstaff.ui can remain relatively compact for 99% of the times it is accessed when user doesn't need to modify those extra instrument details.