So the questions remain about embedded animations. If an animation has a
"starting" and it is embedded, should it pause a sequential animation? This
is the same problem with the the cycle synchronous events. For parallel,
does it delay only itself so that the animations are not parallel anymore?
Async: started, cycleStarted, cycleEnded, ended, paused, resumed
A "starting" event would have to be synchronous to work as I described. The
other "-ing" events probably aren't useful an cause the complications you
describe.
On Tue, Sep 11, 2018 at 10:11 AM Nir Lisker wrote:
> So the "-ed"
Alright, Iv'e queued the multiple event handlers issue after the additional
event types issue.
On Tue, Sep 11, 2018 at 5:15 PM Rick Walker
wrote:
> Thank you, yes that looks like it, I had not seen that comment.
>
> On Tue, 11 Sep 2018 at 09:51, Nir Lisker wrote:
>
>> Hi Rick,
>>
>> Seems to
So the "-ed" events are synchronous? That is, in case of "started", the
animation needs to wait until the event handling finished and then start.
In the case of "starting", the animation would start and call the event
handler asynchronously (like "finished" does now).
Synchronous events can be
Hi Rick,
Seems to me like multiple onFinished event handlers [1]. The first comment
there lists a plan for multiple event handlers in general.
[1] https://bugs.openjdk.java.net/browse/JDK-8091406
On Tue, Sep 11, 2018 at 4:07 PM Rick Walker
wrote:
> Dear Nir,
>
> Please forgive me if I am not
starting: Indicates that the animation is about to start. This is the last
opportunity to change an aspect of the animation that cannot be changed
once the animation has started. PathTransition duration for example.
started: The animation has started.
The "-ed" actions are really what I've had a
Hi Brian,
Thanks for the input. How is "starting" different from "started" etc.?
On Mon, Sep 10, 2018 at 6:23 PM Brian Hudson
wrote:
> I would love to see "Animation needs more events" resolved [1].
>
> Maybe following events: started, paused, resumed, cycleStarted, cycleEnded,
>