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 #296171: fix triggerLayoutAll() for spanners #5424

Merged

Conversation

dmitrio95
Copy link
Contributor

Resolves: https://musescore.org/en/node/296171 (a regression from #5422)

Fixup for 99c7b0d

triggerLayout() and triggerLayoutAll() implementations in Element have an optimization that allows to avoid triggering layout for elements not yet added to a score by checking the element's parent. This optimization is not suitable for spanners since they don't have a parent even when added to a score. This commit adds a missing implementation of Spanner::triggerLayoutAll() that takes this into account.

Fixup for 99c7b0d
triggerLayout() and triggerLayoutAll() implementations in Element
have an optimization that allows to avoid triggering layout for
elements not yet added to a score by checking the element's parent.
This optimization is not suitable for spanners since they don't have
a parent even when added to a score. This commit adds a missing
implementation of Spanner::triggerLayoutAll() that takes this into
account.
@anatoly-os anatoly-os added this to the MuseScore 3.3 milestone Oct 28, 2019
@dmitrio95 dmitrio95 merged commit 0c1de3d into musescore:master Oct 28, 2019
@dmitrio95 dmitrio95 deleted the 296171-spanner-trigger-layout-all branch October 28, 2019 08:37
anatoly-os pushed a commit that referenced this pull request Oct 30, 2019
…-all

fix #296171: fix triggerLayoutAll() for spanners
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