UI changes for text properties/styles in Inspector
OS: macOS High Sierra (10.13), Arch.: x86_64, MuseScore version (64-bit): 3.0.0, revision: 78d0ea2
In current master, the Text Properties and Text Styles dialogs have been removed, and everything is centralized in the Inspector. This is part of a broader design ethos that I wholeheartedly support, involving both #118086: Eliminate most "Properties" dialogs in favor of Inspector for MuseScore 3 and, on the back end, the building of a correspondence between individual elements' properties (in the Inspector) and the global style (in Format / General Style... [which incidentally should probably be renamed since "General" is not needed to distinguish it from the now-eliminated "Text Styles"]).
While there remains a lot unfinished in both of those areas, and there are plenty of bugs to be fixed, Werner's overall vision has already begun to take shape, as is particularly noticeable when one seeks to edit the properties or style of a text element:
Setting aside bugs, there are a few things about this UI that could easily be made more user-friendly.
1) The two disabled (grayed-out) buttons to the right of each setting become enabled when that property is changed from its global style. The button with the counter-clockwise arrow sets the value of the property to that of the style. The other one, with the arrow pointing down, reveals an additional button that will set the value of the style to that of the property. "Set as style" should not be hidden beneath a dropdown; instead, it should be a button equal to "Reset to style" (or, perhaps, the two could be a single divided button).
2) In addition to controlling each parameter independently, there is single large "Reset Text to Style" button that handles all of them at once. As with the individual settings, there should also be a single large "Set As Style" button.
3) The order of the sections in the Inspector is off. Below the section with all the individual properties, there is one with a heading naming what kind of text it is, a menu to assign a style to it (changing all of the individual properties), and a choice of whether to place it above or below the staff. This entire section should be moved above the "Text" section.
4) While at it, the "Substyle" label should be simply "Style"—"substyle" is a term used in the code to help the developers distinguish the new system from the "text styles" that it replaced, but this is not relevant for the user.
5) The gray-green color used to indicate that a property matches its style is unusual, unappealing, and foreign to MuseScore, where aspects of the UI are generally blue.