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
I've been trying to update a plotly graph rapidly and frequently to generate an animation in a react app using window.requestAnimationFrame API, according to this example. Right now, in my update function, I use setState to refresh my states (already bound to my <Plotly /> data prop) and thus trigger plotly to redraw. However, setState is an asynchronous function and it seems to consume too much execution time in between the frame interval. To solve this problem, I'm now trying to use DOM refs and Plotly.animate API to update the graph outside of the React logic. So is there any chance that react-plotly.js will support ref prop in the <Plotly /> component?
Thanks and have a nice day!
The text was updated successfully, but these errors were encountered:
@Sec-ant
Somewhat related to my suggestions here: #242
As noted, a by-product of providing an API based on react hooks is that you can access the ref. Perhaps my examples can give you some inspiration - in my own experience, integrating plotly for specific use-cases can be quite simple and react-plotly can be overly large/inflexible.
I've been trying to update a plotly graph rapidly and frequently to generate an animation in a react app using
window.requestAnimationFrame
API, according to this example. Right now, in my update function, I usesetState
to refresh my states (already bound to my<Plotly />
data prop) and thus trigger plotly to redraw. However,setState
is an asynchronous function and it seems to consume too much execution time in between the frame interval. To solve this problem, I'm now trying to use DOM refs andPlotly.animate
API to update the graph outside of the React logic. So is there any chance that react-plotly.js will supportref
prop in the<Plotly />
component?Thanks and have a nice day!
The text was updated successfully, but these errors were encountered: