Repository navigation
Delayed transitions are not trivial to set up #253
Description
Activity
- added this to the milestone
on Nov 9, 2015 Maybe a PerformanceView that take a PerformanceView on one side, has a startAt argument (default 0.0) and an endAt argument (default 1.0), and implicitly creates the Interval that it applies to the PerformanceView that it exposes?
Sounds about right.
The tricky question here is whether we want to pump frames in the time period before we start the animation. Imagine you schedule an animation to start in 30 seconds. Do we really want to pump frames that whole time or do we want to use a timer to sleep until we're about ready to start?
The downside of using a timer is that the delay won't be measured with the animation clock. That means if you have animation that's running for a minute and another that starts with a delay of 30s, it's not guaranteed that the delayed animation will start on the exact frame where the first animation passes the halfway mark.
IMHO, we should pump frames during the delay for now because that will be correct behavior and file a bug about using less power when waiting for a delayed animation.
It seems like this is trivial now using either Interval or async/await.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 17, 2021
Tuesday Nov 03, 2015 at 18:56 GMT
Originally opened as https://github.com/flutter/engine/issues/1921
We should look at how we can make wrapping a curve in an interval in a ValuePerformance easier.