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
the problem here is a tricky, either we have to disallow y-zoom-in when the y scale range is statically defined, which would be odd / feel broken ux. or we have to return true from sc.auto() when the scale is static but we're viaAutoScaleX = true, which is weird (it means all static scales will scan the data but then pass through the ranging function which will throw the found min/max away). another reason why current auto needs to be split into scan and auto callbacks.
We just bumped into this exact same issue. Should the range function be called regardless of auto or not when we're resetting the zoom with double click?
I also just ran into this issue. I'm assuming I need to "remember" my statically set range (already doing this), and reapply it on the resetting zoom event?
(followup to #914)
the problem here is a tricky, either we have to disallow y-zoom-in when the y scale range is statically defined, which would be odd / feel broken ux. or we have to return true from sc.auto() when the scale is static but we're viaAutoScaleX = true, which is weird (it means all static scales will scan the data but then pass through the ranging function which will throw the found min/max away). another reason why current
auto
needs to be split intoscan
andauto
callbacks.uPlot/src/uPlot.js
Lines 1289 to 1290 in 4b9b927
Peek.2024-01-17.09-31.mp4
https://jsfiddle.net/vmy4hfq8/
The text was updated successfully, but these errors were encountered: