Would a measure(ref) function make sense?

I’ve implemented a ScrollView with reanimated (and gesture handler) since I wanted bidirectional scrolling. Anyways, I’m super happy with the end result. It shows that people who are looking to build consistent experiences across iOS and Android can use gesture handler and reanimated to declare complex high-level components.

However, in my case, I’m lucky because I know statically the upper bound of my x and y scrolling. If the content size would change dynamically, would it make sense to have a measure(ref) function so we can set the scroll upper bound? What are your thoughts on this?

It’s not something that I need but I was just wondering how I would deal with it if this came up.

Thanks for the great work ❤

[mmazzarolo]

@wcandillon I meant that on iOS you get that functionality out of the box by playing with the maximumZoomScale and minimumZoomScale props. They work both vertically and horizontally.

On Android you have to implement it yourself (which is why I’m using the gesture-handler + reanimated).

[wcandillon]

@mmazzarolo I stumbled exactly on the same problem than the one you describe and I didn’t find an adequate solution yet, have you? 😃