1. 17 Jun, 2022 1 commit
  2. 25 May, 2022 1 commit
    • Pierre-Louis's avatar
      Use `curly_braces_in_flow_control_structures` for `foundation`, `gestures`,... · 9cc72df7
      Pierre-Louis authored
      Use `curly_braces_in_flow_control_structures` for `foundation`, `gestures`, `painting`, `physics` (#104610)
      
      * Use `curly_braces_in_flow_control_structures` for `foundation`
      
      * Use `curly_braces_in_flow_control_structures` for `gestures`
      
      * Use `curly_braces_in_flow_control_structures` for `painting`
      
      * Use `curly_braces_in_flow_control_structures` for `physics`
      
      * fix comments
      
      * remove trailing space
      
      * fix TODO style
      9cc72df7
  3. 14 Apr, 2022 1 commit
  4. 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
  5. 08 Oct, 2021 3 commits
  6. 13 Aug, 2021 1 commit
  7. 09 Aug, 2021 1 commit
  8. 08 Jul, 2021 1 commit
  9. 30 Jun, 2021 1 commit
  10. 28 Jun, 2021 1 commit
  11. 10 Jun, 2021 1 commit
  12. 09 Jun, 2021 1 commit
  13. 19 May, 2021 2 commits
  14. 18 May, 2021 1 commit
  15. 17 May, 2021 1 commit
    • Todd Volkert's avatar
      Gesture recognizer cleanup (#81884) · e88a387b
      Todd Volkert authored
      * Gesture recognizer cleanup
      
      1) Make OneSequenceGestureRecognizer.addAllowedPointer()
         call startTrackingPointer(), and change subclasses to
         call super.addAllowedPointer() in place of manually
         calling startTrackingPointer().
      2) Fix addAllowedPointer overrides to take PointerDownEvent
         where some were taking PointerEvent.
      3) Add API documentation to OneSequenceGestureRecognizer
      4) Make the following fields in OneSequenceGestureRecognizer
         private with public getters instead of publicly writable:
         `state`, `primaryPointer`, and `initialPosition`.
      5) Clean up gesture recognizer state in
         OneSequenceGestureRecognizer.didStopTrackingLastPointer.
      
      Fixes #81883
      e88a387b
  16. 07 May, 2021 1 commit
  17. 08 Apr, 2021 1 commit
  18. 12 Jan, 2021 1 commit
  19. 22 Dec, 2020 1 commit
  20. 02 Nov, 2020 1 commit
  21. 17 Sep, 2020 1 commit
    • 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
  22. 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
  23. 06 Aug, 2020 1 commit
  24. 28 Jul, 2020 1 commit
  25. 11 Jun, 2020 1 commit
  26. 07 Jan, 2020 1 commit
  27. 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
  28. 06 Jun, 2019 1 commit
  29. 01 Mar, 2019 2 commits
  30. 13 Feb, 2019 1 commit
  31. 23 Jan, 2019 1 commit
  32. 26 Oct, 2018 1 commit
    • Ian Hickson's avatar
      [O] Cleanup (#23530) · 48a5804d
      Ian Hickson authored
      * Improve documentation
      
      * Potential performance win in hit testing
      
      Rather than copying the list every time we access `path`, this just
      exposes it as an `Iterable`. People who want to copy it can use
      `toList()`.
      
      (This isn't a breaking change since code that expects a `List` is
      still going to get one.)
      
      * Enforce the Oxford Comma.
      48a5804d
  33. 19 Sep, 2018 1 commit
  34. 14 Sep, 2018 1 commit
  35. 12 Sep, 2018 1 commit
  36. 13 Jun, 2018 1 commit
    • Chris Bracken's avatar
      Revert elimination of Dart 1 (#18460) · 2ae48845
      Chris Bracken authored
      fuchsia_tester.dart still assumes Dart 1. Previously, it ran tests directly
      from source, flutter_platform.dart automatically runs a kernel compile when
      operating in Dart 2 mode, but this assumes a functional Dart SDK is available
      in the artifacts directly, and fuchsia_tester.dart mocks out the artifacts
      directory with an empty temp dir.
      
      Remaining work is:
      1. Get the frontend server building as a dependency on Fuchsia.
      2. Patch fuchsia_tester.dart to use a valid Dart SDK and frontend server.
      
      This also reverts migration to Dart 2 typedef syntax.
      
      This reverts commit 6c56bb24. (#18362)
      This reverts commit 3daebd05. (#18316)
      2ae48845