Velocity Tracker getVelocity shouldn't return null when it thinks velocity is 0.0 #8425

Activity

1. eseidelGoogle

   added

   customer: fuchsia

   frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.

   on Feb 28, 2017
2. eseidelGoogle commented on Feb 28, 2017

   

   eseidelGoogle

   on Feb 28, 2017

   Contributor

   More actions

   Presumably @abarth or @Hixie know what to do with this. :) I don't know how to sort this.
3. Hixie

   added

   c: API breakBackwards-incompatible API changesBackwards-incompatible API changes

   on Feb 28, 2017
4. Hixie

   added this to the 2: Make Early Adopters happy milestone on Feb 28, 2017
5. Hixie commented on Feb 28, 2017

   

   Hixie

   on Feb 28, 2017

   Contributor

   More actions

   For now you can work around it by reading the velocity and appending ?? 0.0.
6. Hixie commented on Feb 28, 2017

   

   Hixie

   on Feb 28, 2017

   Contributor

   More actions

   or maybe ?? Offset.zero, or some such. I forget what class the result uses.
7. sethladd

   modified the milestones: 3: Make conferences happyThis milestone has been deleted, 2: Make Early Adopters happy on Mar 21, 2017
8. eseidelGoogle

   modified the milestones: 2: Make Early Adopters happy, 3: Make conferences happyThis milestone has been deleted on Apr 11, 2017
9. Hixie

   self-assigned this

   on Apr 18, 2017
10. Hixie

    added a commit that references this issue on Apr 25, 2017

    Make getVelocity never return null

    ...

    004030d
11. Hixie

    added

    waiting for PR to land (fixed)A fix is in flightA fix is in flight

    on Apr 25, 2017
12. Hixie

    closed this as completedin #9583on Apr 25, 2017
13. Hixie

    added a commit that references this issue on Apr 25, 2017

    Make getVelocity never return null (#9583)

    ...

    24b40d8
14. github-actions commented on Sep 5, 2021

    

    github-actionsbot

    on Sep 5, 2021

    More actions

    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 -v and a minimal reproduction of the issue.
15. github-actions

    locked as resolved and limited conversation to collaborators on Sep 5, 2021