fix #306096: fix incorrect anchor lines coordinates for some element types #6156
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…types In the process of anchor lines reworking some elements appeared to use page coordinate system to describe their anchor lines coordinates while others continued using canvas coordinate system. 4c5e9ed fixed this issue wrongly effectively swapping element types having the incorrect coordinates issue. This PR fixes this inconsistency by ensuring using canvas coordinates for this purpose.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves: https://musescore.org/en/node/306096
In the process of anchor lines reworking some elements appeared to use
page coordinate system to describe their anchor lines coordinates while
others continued using canvas coordinate system. 4c5e9ed fixed this
issue wrongly effectively swapping element types having the incorrect
coordinates issue. This PR fixes this inconsistency by ensuring using
canvas coordinates for this purpose.