Currently, scrolling “inside” a UIPageLayout actually scrolls through the pages. As far as I know, there’s no way to disable that. (Active of the container is already set to false)
I really like the UIPageLayout. Would be annoying if I had to script it myself because I can’t do something simple like disabling a (nice optional, but definitely not nice-enough-to-force-enable) feature. (tbf, now I think about it, scripting it myself wouldn’t be too bad of an idea, as I already do some voodoo like “disabling” pages, but still, ScrollingEnabled would be a nice feature)
That is different, it decides whether or not the transitions are animated. Transitions could still be made through method calls therefore it’s not what you’d want.
I’ve literally just had to make my own because of this issue.
My use case:
I want to be able to filter pages. Because (without the scrolling) I decide when Next/Previous/JumpTo is called, I can make it e.g. ignore the first 3 pages (in my setup, it’s one page, as I have “Hibernation, Home, app1, app2, …”.
A more common use case (and bug?):
The scrolling for ScrollFrames in pages doesn’t work anymore, as it seems that the UIPageLayout’s scrolling takes priority.
A possible use case:
Having a minimap (or whatever) that the user can interact with with the scrollwheel. Currently, even though the scrollwheel event would fire (I think?), it would still scroll the pages.
Yet another use case:
Maybe some people just want the fancy animation (and easy to use :JumpTo() method) and not have the user decide when/how to switch pages. (actuually just a generalized version of my use case)
When you asked for use cases, I thought “how would this behave with scrollframes?”, tested that and saw indeed that the scrollframe doesn’t scroll. (tested in studio yesterday, not online)