We added two properties to the Scroll Constraint options that you can animate and control with the State Machine:
- Scroll Percent X/Y: 0-100% dynamically computed based on the viewport and content size
- Scroll Index: scroll to a specific child item by index
- See docs: https://rive.app/docs/editor/layouts/scrolling
- Scroll Percent X/Y: 0-100% dynamically computed based on the viewport and content size
- Scroll Index: scroll to a specific child item by index
- See docs: https://rive.app/docs/editor/layouts/scrolling
Comments
@rive.app We're using Rive animations as animated sections/backgrounds (web), controlled by a ScrollPct (0>100) input via the runtime.
I understand how the scroll feature works within a Rive file, but can/should we use it to replace our Number input implementation? Any benefits?
Thanks! :)