Resolves #6612 #6649
Merged
Resolves #6612 #6649
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
17 tasks
davepagurek
approved these changes
Dec 23, 2023
This was referenced Oct 31, 2024
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 #6612
Looks like I introduced this bug when adjusting these outputs to account for matrix transformations. Oops! I remembered to multiply the canvas dimensions by the pixel density in_getArea but not _getPos. Here I've added that multiplication to _getPos so that textOutput and gridOutput describe positions correctly on high density displays.
Changes:
Screenshots of the change:
PR Checklist
npm run lintpasses