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
useAnimationController would be more useful if it included:
Ability to auto-play forward or back, or a callback that lets us kick off the animation
Ability to delay the autoplay
Ability to automatically rebuild on tick
Currently because AnimController does not have this we have to often use an "imperitive escape-hatch" of useEffect to start our animations, and add extra lines of boilerplate to tick our widgets:
I worry that TAB is not imperative enough. This is a use case situation where we want to use AC for its flexibility, but also kick it off when we first load.
In other word TAB works great when you want to initially play something, but you are then forced into continuous animation, no ability to do from: 0 or whatever you need, so it's very limited in the roles it can play for dynamic animation.
The main goal to this proposal is to just more fully flesh out the declarative syntax for AC, so we're not forced into imperative and less readable useEffect hooks anytime we want to delay the start, or auto-play. It's not changing the role, it's just cleaning up syntax and making the use of imperative calls less common.
Unless you're thinking a TAB style hook, that still has forward() calls etc? That would definitely work fine.
useAnimationController would be more useful if it included:
Currently because AnimController does not have this we have to often use an "imperitive escape-hatch" of
useEffect
to start our animations, and add extra lines of boilerplate to tick our widgets:This could better be represented declaritively as:
The text was updated successfully, but these errors were encountered: