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

fix #316096, fix #305093: custom gliss text reverts to default "gliss" #7315

Merged
merged 1 commit into from
Jan 28, 2021

Conversation

MarcSabatella
Copy link
Contributor

Resolves: https://musescore.org/en/node/316096
Resolves: https://musescore.org/en/node/305093

Issue is that customized gliss text reverts back to the default "gliss".
In all 3.x versions, this happened after saving, reloading,
then making any style change.
In 3.6, this happens immediately on the save/reload.
Cause is that the property was never makred unstyled on read.
Fix is to change the plain setting of "_text" with
a call to readProperty() on Pid::GLISS_TEXT.

Resolves: https://musescore.org/en/node/316096
Resolves: https://musescore.org/en/node/305093

Issue is that customized gliss text reverts back to the default "gliss".
In all 3.x versions, this happened after saving, reloading,
then making any style change.
In 3.6, this happens immediately on the save/reload.
Cause is that the property was never makred unstyled on read.
Fix is to change the plain setting of "_text" with
a call to readProperty() on Pid::GLISS_TEXT.
@MarcSabatella
Copy link
Contributor Author

MarcSabatella commented Jan 27, 2021

FWIW, two different reports of this bug came in over the weekend. So it wasn't part of the batch of Trello issues I added last week, but definitely worth including.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants