-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Animate API #802
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
Animate API #802
Conversation
7bf81a0
to
06d1e46
Compare
d14cc15
to
fbfbf53
Compare
0f92220
to
7447887
Compare
@rreusser what's the current status of this PR? |
All reactions
Sorry, something went wrong.
Currently trying to solve race condition with the autolayout feature. I was cheating a bit and timing transitions independently of d3's execution of the transitions, but that tends to result in problematic race conditions in which every now and then a d3 update comes through after the transitions has been redrawn. I feel like I'm attempting to group my transitions correctly, but the just don't group. @monfera, do you have experience with grouping d3 v3 transitions? I put large chunks that create more transitions inside a Also, @etpinard, are you aware of a straightforward way to temporarily disable autorange while performing a redraw? With the cleanup, it now autoranges when |
All reactions
-
👍 1 reaction
Sorry, something went wrong.
7447887
to
0946987
Compare
To do:
|
All reactions
Sorry, something went wrong.
} | ||
|
||
if(xObj.visible && isNumeric(coords.y) && | ||
if(xObj.visible && isNumeric(coords.x) && |
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.
why?
Sorry, something went wrong.
All reactions
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.
Oh wow, good catch. 😬
Sorry, something went wrong.
All reactions
f43ac01
to
4e88184
Compare
@rreusser a very well-deserved 💃 |
All reactions
-
🎉 1 reaction
Sorry, something went wrong.
An epic piece of work @rreusser ! |
All reactions
Sorry, something went wrong.
- as of PR #802, scatter traces are no longer purged in the per-subplot cartesian plot step - to maintain consistency between transitions. - While the scatter plot module can remove individual 'visible: false' traces, when all scatter traces are restyled to 'visible: false' the scatter plot module is currently not called!
- as of PR #802, scatter traces are no longer purged in the per-subplot cartesian plot step - to maintain consistency between transitions. - While the scatter plot module can remove individual 'visible: false' traces, when all scatter traces are restyled to 'visible: false' the scatter plot module is currently not called!
I made a mess of #717 by letting it go too long and performing a bad merge/rebase or two. This PR handles animation and attempts to get all tests passing.
Checklist:
.animate
queues framespurged
: https://github.com/plotly/plotly.js/blob/master/src/plots/plots.js#L779