flyTo should support an explicit duration option #1854
Assignees
Labels
Comments
1ec5
added a commit
that referenced
this issue
Dec 22, 2015
Added flyTo() options that are based on observable properties, so that suitable values can be chosen without guessing and checking. Also documented local variables in flyTo(), based on the paper that describes this algorithm, because the names are non-obvious. Fixes #1854.
1ec5
added a commit
that referenced
this issue
Dec 22, 2015
Added flyTo() options that are based on observable properties, so that suitable values can be chosen without guessing and checking. Also documented local variables in flyTo(), based on the paper that describes this algorithm, because the names are non-obvious. Fixes #1854.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
flyTo()currently chooses a duration based onspeedandcurveoptions, neither of which correspond to physical measurements. (They correspond to V and ρ in this algorithm.) This duration tends to be sensible but isn’t entirely obvious.flyTo()should expose the duration that it computes internally, so that developers can time other animations in tandem with the flight./ref #1429
/cc @lucaswoj
The text was updated successfully, but these errors were encountered: