-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Additional animation issues #933
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
Comments
@etpinard @monfera Curious to hear your thoughts on the frame merging issue. Animations currently 1) expand objects (e.g.
Long story short, I need to fix a couple bugs, so I either need to commit to the current approach and make it 100% correct, or I need to reevaluate and make the right choice about the most straightforward and sensible way for this to work. |
After a brief discussion, the conclusion is that the current behavior is best: attribute strings are good for single properties but awkward for whole frames (which would then need every property attribute-stringed, which wouldn't really be acceptable). Then working through transform array logic… |
After #956 it would be easy
|
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson |
I've found some additional issues related to animation that should be fixed ASAP:
Plotly.update
?)Lib.syncOrAsync
(see first try in Move plotly.animate to Lib.syncOrAsync #1693)The text was updated successfully, but these errors were encountered: