Font settings for a tablature staff fail to activate on the first attempt (Tab staff properties>Advanced style properties>Edit text style)

Issue type

UX/Interaction bug (incorrect behaviour)

Description with steps to reproduce

This behavior is present in the 4.7 nightly. It may also be present in 4.6.2 but any public version of 4.6 crashes on opening any score or any new score, so I can't test to see.

Steps to replicate:

• New score > Solo > Guitar + tablature
• Add a few notes to the score
• Choose Staff/Part Properties for the tablature staff
• Click the Advanced Style Properties button
• Click the Edit Text Style buttons
• Set the Font to something distinctly different, like Comic San or Chalkduster or a dingbats font

https://github.com/user-attachments/assets/0d019232-396b-485b-81b1-27cfb17094bf

RESULT (as expected): The fret numbers in the TAB staff immediately update

• Now increase the font size

RESULT(as expected): The fontsize of the TAB numbers immediately updates

• Next, confirm and exit by clicking: OK, OK, OK

UNEXPECTED RESULT: On clicking the final OK the tablature fret numbers display as they did at the outset, not according to the properties just entered in the dialog, which are indeed still intact!

Return to Edit text style via:

• Choose Staff/Part Properties for the tablature staff
• Click the Advanced Style Properties button
• Click the Edit text style buttons

Note that the properties are as you had set them (however they DO NOT affect the display of TAB fret numbers in the score.)

• Then again confirm and exit by clicking: OK, OK, OK

RESULT: NOW the frets display according to the proper values previously set.

In which versions of MuseScore Studio is this issue present?

4.7 nightly

Regression

No

Operating system

MacOS 13.7.8

Additional context

This was previously reported in a Github discussion:

https://github.com/orgs/musescore/discussions/29593

... and on .org:

https://musescore.org/en/node/382441#comment-1305477

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible