Matrices computation improvements and various fixes, including encryption enhencement #75
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
Optimize matrices computations
This was referenced May 5, 2015
hgy29
changed the title
ar2rsawseen
added a commit
that referenced
this pull request
May 8, 2015
Matrices computation improvements and various fixes, including encryption enhencement
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.
Try to avoid floating points ops and have a shorter CPU path when dealing with simplest matrix types (ie, translate only, 2D only, 3D only, etc)
Make hitTestPoint work again the way it used to by changing matrix inversion behavior