1. 01 Oct, 2020 1 commit
  2. 17 Sep, 2020 2 commits
    • Matěj Žídek's avatar
      Minor docs updates (#64966) · 827cbc35
      Matěj Žídek authored
      827cbc35
    • Jonah Williams's avatar
      Deprecate VelocityTracker default constructor and added... · b1d17c91
      Jonah Williams authored
      Deprecate VelocityTracker default constructor and added VelocityTracker.withKind constructor (#66043)
      
      We've gotten feedback that the VelocityTracker change was disruptive, though it did not break any of the flutter framework or customer tests. In order to make the change non-breaking, PointerDeviceKind parameter can be made optional.
      
      Nevertheless, this parameter should be provided so that the existing touch handlers can use more accurate gestures on mouse/stylus inputs, so we can encourage this by deprecating the default constructor and pointing users towards the VelocityTracker.withKind constructor that takes a non-optional parameter
      b1d17c91
  3. 16 Sep, 2020 1 commit
  4. 08 Sep, 2020 1 commit
    • Jonah Williams's avatar
      [framework] make hit slop based on device pointer kind for drag/pan/scale gestures (#64267) · 29898812
      Jonah Williams authored
      Currently the framework uses fairly large "hit slop" values to disambiguate taps from drags/pans. This makes sense on touch devices where the interaction is not very precise, on mice however it can feel as if the UI is lagging. This is immediately noticeable on our infra dashboard, where it takes almost half of a grid square of drag before the actual drag kicks in.
      
      One potential solution is to always use smaller constants depending on whether the interaction is mouse or touch based. The only reasonable choice is to use the pointer device kind and not target platform - same platform can have different input sources. This requires exposing the pointer device kind in a few new places in several of the gesture detectors, and using the enum to compute the correct hit slop from an expanded set of constants.
      
      This almost works, however there are a few places (notably ListViews) which uses the touch hit slop as a default value in scroll physics. It does not seem like it will be easy to disambiguate a user provided scroll physics constant from the default and/or adjust it somehow - this might require significant changes to scroll physics which I have left out of this PR.
      
      This PR does not adjust:
      
      kTouchSlop used in scroll_physics.dart's minFlingDistance
      kTouchSlop used in PrimaryPointerGestureRecognizer/LongPressGestureRecognizer
      29898812
  5. 28 Aug, 2020 1 commit
  6. 27 Aug, 2020 1 commit
  7. 24 Aug, 2020 2 commits
  8. 20 Aug, 2020 2 commits
  9. 12 Aug, 2020 1 commit
  10. 08 Aug, 2020 1 commit
  11. 06 Aug, 2020 2 commits
  12. 28 Jul, 2020 3 commits
  13. 24 Jul, 2020 1 commit
  14. 14 Jul, 2020 1 commit
  15. 08 Jul, 2020 1 commit
  16. 07 Jul, 2020 3 commits
  17. 11 Jun, 2020 2 commits
  18. 02 Jun, 2020 1 commit
  19. 18 May, 2020 1 commit
  20. 11 May, 2020 1 commit
    • Tong Mu's avatar
      System mouse cursors (#54171) · 7f8cb7f8
      Tong Mu authored
      Adds the basic framework for the mouse cursor system. 
      
      * Adds MouseRegion.cursor
      * Adds SystemMouseCursors
      * Adds mouseCursor to some widgets
      7f8cb7f8
  21. 06 May, 2020 1 commit
  22. 01 May, 2020 1 commit
  23. 06 Apr, 2020 1 commit
  24. 27 Mar, 2020 1 commit
  25. 20 Mar, 2020 1 commit
  26. 13 Mar, 2020 1 commit
  27. 11 Mar, 2020 1 commit
    • Greg Spencer's avatar
      Convert Diagnosticable to a mixin (#51495) · 210f4d83
      Greg Spencer authored
      This converts Diagnosticable to be a mixin instead of an abstract class, so that it can be used to add diagnostics to classes which already have a base class.
      
      It leaves in place the DiagnosticableMixin mixin, since there are some plugins that are still using it, and removing it would mean that those plugins wouldn't work with master branch Flutter anymore. DiagnosticableMixin will be removed once this mixin version of Diagnosticable makes its way to the stable branch.
      210f4d83
  28. 21 Feb, 2020 1 commit
  29. 31 Jan, 2020 1 commit
  30. 28 Jan, 2020 2 commits