Side note, we should probably have posAbove and posBelow for chord symbols in generate, map the offset in "chord symbol A" text style to the general posAbove, and have an independent offset in the "chord symbol b" text style. This will allow chord symbols a & b to have separate offsets as style settings, so style b can default to a higher position. Although unless there are further code changes to support it, you'll have to turn off autoplace in order for two chord symbols (one with style a, the other with style b) on the same note to actually lay out correctly.
Comments
Side note, we should probably have posAbove and posBelow for chord symbols in generate, map the offset in "chord symbol A" text style to the general posAbove, and have an independent offset in the "chord symbol b" text style. This will allow chord symbols a & b to have separate offsets as style settings, so style b can default to a higher position. Although unless there are further code changes to support it, you'll have to turn off autoplace in order for two chord symbols (one with style a, the other with style b) on the same note to actually lay out correctly.
Guess I'll take a look at this at some point :)
https://github.com/musescore/MuseScore/pull/4212
Fixed in branch master, commit 8a561c6ec3
fix #278166: chord symbols don't have above/below like other text types
Fixed in branch master, commit 5b2d7550aa
Merge pull request #4212 from jthistle/278166-chord-symbols-above-below
fix #278166: chord symbols don't have above/below like other text types
Automatically closed -- issue fixed for 2 weeks with no activity.