On Tue, 6 Dec 2022 13:09:25 GMT, Kevin Rushforth <k...@openjdk.org> wrote:
>> I don't mind changing it, but I think those durations are relative, so >> `Duration.millis(0)` means "don't wait". I'm not sure I follow the >> recommendation. > > To expand on what Ambarish said, if you have a repeating timeline, any action > that is done as part of a `KeyFrame` at time 0 will be executed immediately > (with no delay) after an action that is done as part of the `KeyFrame` at > time `last`. So in the current test (which mimics the manual test program > submitted with the bug), what you have is: > > > set scene 1 > wait 200 msec > set scene 2 > set scene 1 // immediately after the previous > wait 200 msec > ... > > > To do what you want, you might add a third "no-op" `KeyFrame` at time 400 > (you could also change the time values for the two existing `KeyFrame`s to > 200 and 400, respectively, but then no scene would be set for the first 200 > msec of the test when the timeline first plays). I've changed it as requested, but I must confess I didn't get the point. But don't waste time to explain, somewhere in the future it will become clear. ------------- PR: https://git.openjdk.org/jfx/pull/940
