Multiple animate() calls

ID:1935102
 
Sep 12 2015, 11:41 pm
Resolved
It is now possible to animate different values in different ways for the same object. Call animate() with the new ANIMATION_PARALLEL flag to setup a parallel animation.
Applies to:DM Language
Status: Resolved (511.1348)
This issue has been resolved.
Currently you can only have one animate() call running at once on an atom. You can't do something to the tune of,
animate(atom, alpha = 0, time = 20, easing = SINE_EASING | EASE_OUT)
animate(atom, pixel_y = 128, time = 10, easing = SINE_EASING | EASE_IN)


Whilst I understand why you can't do an animate() with the same args as another one, surely this should be possible in some way.
Sep 13 2015, 1:09 am
Try the following:
animate(atom, alpha = 0, time = 20, easing = SINE_EASING | EASE_OUT)
animate(pixel_y = 128, time = 10, easing = SINE_EASING | EASE_IN)
Sep 13 2015, 1:16 am
That's erm, interesting syntax. How does that work with multiple animate()s being called on multiple atoms?

Like, atom A gets animate() called, then atom B gets animate() called in a seperate function, then animate() gets called on A again without A as the target arg. Will the second animate() execute on A or B?
Sep 13 2015, 1:17 am
In response to GinjaNinja32
That will affect alpha, then pixel_y. This request is for animating variables independently of others.
Sep 13 2015, 2:43 am
From what I understand, this will require Lummox to basically rework how animate() handles appearances and possibly how appearances are defined and handled altogether. This is definitely one of the more requested features in regards to animation, but I don't think Lummox has any plans on rewriting a lot of that functionality yet. I'm very hopeful that it's one of the things that gets addressed before appearances have too much code stacked on them to be worth the effort to change.
Sep 13 2015, 10:42 am
I don't think this request would be negatively impacted by future appearance features. It would however be a little annoying to manage. Still I do see the utility, so it's been on my mind. Probably 509 is an unlikely target for it, though.
Sep 13 2015, 6:05 pm
Well, it's good to know that it's at least somewhere in the pipeline. :)
Jul 13 2016, 10:39 am
Lummox JR resolved issue with message:
It is now possible to animate different values in different ways for the same object. Call animate() with the new ANIMATION_PARALLEL flag to setup a parallel animation.
Jul 14 2016, 1:37 pm
I'll boil an egg in honour of this moment.