Skip to content
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

Merged
merged 5 commits into from
Oct 22, 2024
Merged

Conversation

cyrush
Copy link
Member

@cyrush cyrush commented Oct 18, 2024

adds a transform filter that supports:

  • translate
  • scale
  • rotate
  • transform via an arbitrary 4x4 transformation matrix

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?
Copy link
Member Author

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.

Copy link
Member

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

Copy link
Contributor

@nicolemarsaglia nicolemarsaglia left a 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 (:

@cyrush cyrush merged commit bd1182d into develop Oct 22, 2024
22 checks passed
@cyrush cyrush deleted the task/2024_10_add_transform_filter branch October 22, 2024 17:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants