Animate.delay has no effect when used with Animate.autoPlay=false

[lukepighetti]

I keep getting this warning. I have autoPlay set to an external boolean because they are waiting for some state to change before playing. But this throws a ton of warnings in my console.

What's the proper way to disable an animation to be played later?

Or how do I suppress these warnings?

flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.delay has no effect when used with Animate.autoPlay=false<…>
flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.onPlay is not called when Animate.autoPlay=false<…>
flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.delay has no effect when used with Animate.autoPlay=false<…>
flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.onPlay is not called when Animate.autoPlay=false<…>
flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.delay has no effect when used with Animate.autoPlay=false<…>
flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.onPlay is not called when Animate.autoPlay=false<…>
flutter: \^[[48;5;229m\^[[38;5;0m[flutter_animate] Animate.delay has no effect when used with Animate.autoPlay=false<…>

[gskinner]

As in, you are setting autoPlay to true when the state changes in order to make it play?

[lukepighetti]

yes

it's worth mentioning that this animation is a repeating animation

[gskinner]

Gotcha. That is good to know, because of course usually you'd use target.

For now, you can obviously ignore those warnings (I know that's not ideal), or even just edit the warn.dart file to disable warnings (I should add a flag for that).

You can also apply / remove the animation based on state, but that can add its own complexity.

Widget foo = spinner;
if (_myState) foo = foo.animate().etc();
// and of course, this could be wrapped in a function / getter to make it cleaner.

I'll give this a bit of thought, but I'm also very open to suggestions or thoughts as you play around with it.

[lukepighetti]

for me the benefit of flutter_animate is being able to chain a bunch of animations together and then drive them declaratively whether it has a target or is a repeating animation. target would be driven by value and repeating animation would be driven by boolean, probably with false optionally resolving something like opacity to 0 (but that could be done with a separate animation)

an example would be a card that breathes up and down in a loop when value is true, but fades out when value is false