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
Hi there.
I've been using the Scroller for my last university project and it's really great!
But there's an error in logic that __computeScrollMax uses to compute the __maxScroll values.
As it is at the moment, the values computed are too large when zooming in on canvas elemenets:
Actually, this seems quite odd, but the logic works differently in different examples.
For example when scaling the context of the canvas (ctx.scale) my logic works, but when redrawing the components like you do in the canvas example your logic works.
Maybe there should be a way to override the default logic in case of a different implementation of the rendering?
It mainly depends on whether your properties apply zooming on top of dimensions or the other way around. This is the reason why we recompute the dimensions and positions based on zooming in some examples and do not so in others.
Hi there.
I've been using the Scroller for my last university project and it's really great!
But there's an error in logic that
__computeScrollMax
uses to compute the__maxScroll
values.As it is at the moment, the values computed are too large when zooming in on canvas elemenets:
I've corrected the problem here:
Cheers!
The text was updated successfully, but these errors were encountered: