Transformation bug #77
Closed
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
|
I just took a look at the issues and found out that I am trying to solve #27 |
|
Would be cool to have #27 fixed. |
|
I am closing this one as it is a dup of #27. |
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.
hi @xclud,
if you have not scaled or rotated the image, translating it to any direction just recenters it.
I started getting into the reason for this bug but for now, all my commits are about refactoring.
I found out the reason for this, which is when the image is scaled, the distanceToPoint's are never more than 1, while when it is not, usually some of them are bigger than 1, which causes recentering the image.
I will start trying to fix this bug tomorrow, any help from you is appreciated.