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
Let's say that you have a chart with limits min/max = 'original', so that panning/zooming never exceeds the range of data points.
Then new data points arrive. (Like another day of data points with time x-axis, and we drop the oldest day of data points.)
In the initial chart display--or after a resetZoom()--when the new data points arrive, they get displayed.
But if you're zoomed and/or panned, and new data points arrive, then you cannot visit the new data points (by zooming out or panning over); the original range of data points is set in stone due to storeOriginalScaleLimits().
A partial workaround for zooming out is to call resetZoom() once you've zoomed all the way out:
No workaround for when you're zoomed in or panning.
I know you could update limits min/max with the range of the new data (like in #649), as it arrives, but that information may not be available, and not as convenient.
The text was updated successfully, but these errors were encountered:
Let's say that you have a chart with limits min/max = 'original', so that panning/zooming never exceeds the range of data points.
Then new data points arrive. (Like another day of data points with time x-axis, and we drop the oldest day of data points.)
In the initial chart display--or after a
resetZoom()
--when the new data points arrive, they get displayed.But if you're zoomed and/or panned, and new data points arrive, then you cannot visit the new data points (by zooming out or panning over); the original range of data points is set in stone due to
storeOriginalScaleLimits()
.A partial workaround for zooming out is to call
resetZoom()
once you've zoomed all the way out:No workaround for when you're zoomed in or panning.
I know you could update limits min/max with the range of the new data (like in #649), as it arrives, but that information may not be available, and not as convenient.
The text was updated successfully, but these errors were encountered: