1. 05 Oct, 2022 1 commit
  2. 10 Aug, 2022 1 commit
  3. 22 Jul, 2022 1 commit
  4. 21 Jul, 2022 2 commits
  5. 19 Jul, 2022 1 commit
  6. 17 Jun, 2022 1 commit
  7. 14 Apr, 2022 1 commit
  8. 13 Apr, 2022 1 commit
    • Callum Moffat's avatar
      Support trackpad gestures in framework (#89944) · 30a50180
      Callum Moffat authored
      * Implement trackpad gestures in framework
      
      * Touch and Pan/Zoom pointers have separate IDs now
      
      * Handle trackpad pointer device type
      
      * Respect supportedDevices for pan/zoom events
      
      * Update after rebase
      
      * Fix check failures
      
      * Avoid error with very short drags
      
      * Address feedback
      
      * Refactor drag event handler
      
      * Address more feedback
      
      * Add some missing punctuation
      30a50180
  9. 01 Feb, 2022 1 commit
  10. 23 Aug, 2021 1 commit
  11. 09 Aug, 2021 1 commit
  12. 08 Jul, 2021 1 commit
  13. 22 Mar, 2021 1 commit
  14. 17 Dec, 2020 1 commit
  15. 09 Nov, 2020 1 commit
  16. 31 Oct, 2020 1 commit
  17. 12 Oct, 2020 1 commit
  18. 02 Oct, 2020 1 commit
    • Tong Mu's avatar
      Lazily compute PointerEvent's transformed positions (#63813) · 74fe6bff
      Tong Mu authored
      * PointerEvent.local* properties are calculated lazily; other properties are delegated to original.
      * Transformed PointerEvent becomes a subclass of its original class.
      * Unnamed constructors no longer accepts transform and origin.
      74fe6bff
  19. 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
  20. 24 Aug, 2020 1 commit
  21. 20 Aug, 2020 1 commit
  22. 08 Aug, 2020 1 commit
  23. 06 Aug, 2020 1 commit
  24. 28 Jul, 2020 1 commit
  25. 14 Jul, 2020 1 commit
  26. 08 Jul, 2020 1 commit
  27. 07 Jul, 2020 3 commits
  28. 11 Jun, 2020 1 commit
  29. 01 May, 2020 1 commit
  30. 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
  31. 21 Feb, 2020 1 commit
  32. 05 Dec, 2019 1 commit
    • Greg Spencer's avatar
      Normalizes all of the "See also" blocks in comments. (#46121) · c6fe7bb9
      Greg Spencer authored
      This normalizes all of the "See also" blocks in comments so that they conform in style.
      
      They all look like this now:
      
        /// See also:
        ///
        ///  * [MyFavoriteWidget], because it's cool.
        class Foo {}
      
      I removed some useless "See also" blocks, and added commentary to ones that were just "bare" references.
      
      This is my penance for adding so many bullets that are "-" instead of "*". :-)
      c6fe7bb9
  33. 03 Dec, 2019 1 commit
  34. 27 Nov, 2019 1 commit
    • Ian Hickson's avatar
      License update (#45373) · 449f4a66
      Ian Hickson authored
      * Update project.pbxproj files to say Flutter rather than Chromium
      
      Also, the templates now have an empty organization so that we don't cause people to give their apps a Flutter copyright.
      
      * Update the copyright notice checker to require a standard notice on all files
      
      * Update copyrights on Dart files. (This was a mechanical commit.)
      
      * Fix weird license headers on Dart files that deviate from our conventions; relicense Shrine.
      
      Some were already marked "The Flutter Authors", not clear why. Their
      dates have been normalized. Some were missing the blank line after the
      license. Some were randomly different in trivial ways for no apparent
      reason (e.g. missing the trailing period).
      
      * Clean up the copyrights in non-Dart files. (Manual edits.)
      
      Also, make sure templates don't have copyrights.
      
      * Fix some more ORGANIZATIONNAMEs
      449f4a66
  35. 26 Nov, 2019 1 commit
  36. 22 Nov, 2019 1 commit
  37. 16 Nov, 2019 1 commit