-
Notifications
You must be signed in to change notification settings - Fork 67
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
add ascent transform filter #1403
Conversation
PointTransform::SetTransform(const double *matrix_values) | ||
{ | ||
// TODO: row vs col vs matrix vs array, what is the best | ||
// order for users to provide flat values to matrix? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: this order seems good.
I googled some example transform matrices and threw them in easily.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
scale then rotate then translate
T * R * S
I didn't look at the code but is that what this is about? https://gamedev.stackexchange.com/questions/16719/what-is-the-correct-order-to-multiply-scale-rotation-and-translation-matrices-f
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the unit test images! But it looks like you forgot to add the actual unit tests (:
adds a transform filter that supports: