You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 3, 2024. It is now read-only.
I was using the initial autorange values to "hold" my plotly.graph_objs.Layout plot axes from recalculating when dynamically adding or removing plotly.graph_objs.scatter.Markers. Three questions:
Is there some place else I can read Layout axes range values after they have been calculated by the autorange function?
Is there a better way to "hold" a plotly.graph_objs.Layout to the initial autorange values?
Can the plotly.graph_objs.Layout axes autorange function be invoked directly?
The text was updated successfully, but these errors were encountered:
Just to add that I've noticed the same thing, particularly noticeable when dcc.Interval is being used to refresh/stream data in real-time. I can programmatically set the axes range, but am not able to retrieve the figure layout range prop in order to be able to "hold" the figure.
I suspect the cause is from commit 7b48b18 in v0.30.2: (@valentijnnieman), though I have no clue why R.clone() would be failing.. seems like a deep copy is meant to prevent this type of issue.
edit: I was specifically grabbing from the range (Graph.figure.layout.yaxis.range)
Thanks for pointing our the new feature. I made a comment in the forums that the View still resets unless I necessarily interact with the Figure (Zoom in, out, autoscale, etc) which is not ideal. I would like to preserve the IU state without doing that. You can use cchridyp's example here to see what I mean https://community.plot.ly/t/preserving-ui-state-like-zoom-in-dcc-graph-with-uirevision/15793.
I was using the initial autorange values to "hold" my plotly.graph_objs.Layout plot axes from recalculating when dynamically adding or removing plotly.graph_objs.scatter.Markers. Three questions:
The text was updated successfully, but these errors were encountered: