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.

Sign up for GitHub

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

Jump to bottom

Path.getPointAt Works Differently from Path.beginning and Path.ending #593

Open
jonobr1 opened this issue Jan 12, 2022 · 0 comments
Open

Path.getPointAt Works Differently from Path.beginning and Path.ending #593

jonobr1 opened this issue Jan 12, 2022 · 0 comments
Labels
enhancement

Comments

@jonobr1
Copy link
Owner

jonobr1 commented Jan 12, 2022

Is your feature request related to a problem? Please describe.
Yes, first described here by @dickinson0718. The method getPointAt on primitive shapes of Two.js look at the t value differently than when using the beginning or ending properties.

Describe the solution you'd like
These three properties should all interpret the t value in the same way.

Additional context
This affects the ability for developers to get the coordinates that they need to realize the experiences they're building.
@jonobr1 jonobr1 changed the title Path.getPointAt Works Differently Than Path.beginning and Path.ending Path.getPointAt Works Differently from Path.beginning and Path.ending Jan 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jonobr1