Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chord style does not get updated in view when loading a style file #21914

Closed
LawrenceWence opened this issue Mar 13, 2024 · 1 comment · Fixed by #21955
Closed

chord style does not get updated in view when loading a style file #21914

LawrenceWence opened this issue Mar 13, 2024 · 1 comment · Fixed by #21955
Assignees
Labels
engraving P1 Priority: High

Comments

@LawrenceWence
Copy link

Issue type

Engraving bug (incorrect score rendering)

Bug description

If you have a score sheet with chords with default style and load a style file that has chord style set to "Jazz" the "Jazz" style will not become visible.

Easy workaround: Go to chord style setting afterwards and change it manually to "Standard" and back to "Jazz".

Steps to reproduce

  • Have score with standard chord style and chords.
  • Have a style file that has "Jazz" chord style, load that style.
  • chord symbols will not view in Jazz style

Screenshots/Screen recordings

No response

MuseScore Version

4.2.1 and master from 13.03.2024

Regression

I don't know

Operating system

Windows 11

Additional context

No response

@bkunda bkunda added the needs info More information is required before action can be taken label Mar 15, 2024
@oktophonie oktophonie removed the needs info More information is required before action can be taken label Mar 15, 2024
@oktophonie oktophonie added the P1 Priority: High label Mar 15, 2024
@LawrenceWence
Copy link
Author

thanks for solving that so fast. I tested this with latest master and can confirm it's fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engraving P1 Priority: High
Projects
Development

Successfully merging a pull request may close this issue.

5 participants