Repository navigation
AnimatedValue should not be mutable #216
Description
Wednesday Oct 21, 2015 at 16:51 GMT
Originally opened as https://github.com/flutter/engine/issues/1709
Rather than AnimatedValue being mutable, it should just represent a begin/end range and have an API that, given a value 0.0..1.0, returns a lerp over that range.
Alternatively, we could make AnimatedValue take an object that represents 0..1, a direction, and a change notification API, and exposes a value in the range begin..end and a change notification API. That way you would just plug AnimatedValues straight into the things they were animated by.
Activity
abarth commentedon Jan 21, 2016
Fixed.
github-actions commentedon Aug 17, 2021
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.