- 16 Nov, 2021 1 commit
-
-
Justin McCandless authored
-
- 08 Oct, 2021 3 commits
-
-
Ian Hickson authored
-
Zachary Anderson authored
This reverts commit 5fd259be.
-
Ian Hickson authored
-
- 09 Aug, 2021 1 commit
-
-
Jonah Williams authored
-
- 19 May, 2021 3 commits
-
-
Todd Volkert authored
This is a re-application of https://github.com/flutter/flutter/pull/81884, but with https://github.com/flutter/flutter/pull/82834 landed first. Fixes https://github.com/flutter/flutter/issues/81883
-
Tong Mu authored
-
Todd Volkert authored
They should have been taking a PointerDownEvent. This change was originally included in #81884, but that had to be reverted because it broke Google testss. This sub-part of that larger change needs to be made first in order to allow for a phased rollout in a way that won't break Google tests. https://github.com/flutter/flutter/issues/81883
-
- 18 May, 2021 1 commit
-
-
Todd Volkert authored
This reverts commit e88a387b.
-
- 17 May, 2021 1 commit
-
-
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
-
- 14 May, 2021 1 commit
-
-
xubaolin authored
-
- 07 May, 2021 1 commit
-
-
Kate Lovett authored
-
- 03 May, 2021 1 commit
-
-
Jonah Williams authored
-
- 16 Feb, 2021 1 commit
-
-
Michael Goderbauer authored
-
- 06 Nov, 2020 1 commit
-
-
Tong Mu authored
This relands #68587
-
- 02 Nov, 2020 1 commit
-
-
Greg Spencer authored
-
- 28 Oct, 2020 1 commit
-
-
xubaolin authored
Fixes a bug where selection handles sometimes showed on web.
-
- 23 Oct, 2020 1 commit
-
-
Jonah Williams authored
This reverts commit bde85ea3.
-
- 22 Oct, 2020 1 commit
-
-
xubaolin authored
* Fix mutiple pointers bug * Add unit test case * Remove unnecessary map clone
-
- 10 Oct, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 01 Oct, 2020 1 commit
-
-
Phil Quitslund authored
-
- 17 Sep, 2020 1 commit
-
-
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
-
- 08 Sep, 2020 1 commit
-
-
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
-
- 12 Aug, 2020 1 commit
-
-
LongCatIsLooong authored
-
- 28 Jul, 2020 1 commit
-
-
Alexandre Ardhuin authored
-
- 11 Jun, 2020 1 commit
-
-
Alexandre Ardhuin authored
* add language version 2.8 in packages/flutter * enable non-nullable analyzer flag
-
- 27 Nov, 2019 1 commit
-
-
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
-
- 26 Nov, 2019 1 commit
-
-
Alexandre Ardhuin authored
* implicit-casts:false in flutter/lib/src/gestures * address review comments
-
- 02 Oct, 2019 1 commit
-
-
Tong Mu authored
* Extracts the logic of TapGestureRecognizer into an abstract class BaseTapGestureRecognizer * Fixes ModalBarrier unable to dismiss when competing
-
- 27 Aug, 2019 1 commit
-
-
Tong Mu authored
Add "OneSequenceRecognizer.resolvePointer". Fix DragGestureRecognizer crash on multiple pointers (#39017) * Add drag tests * Add resolvePointer * Correct monodrag implementation * Fix some addTearDown
-
- 31 Jul, 2019 1 commit
-
-
Justin McCandless authored
You can drag the cupertinoscrollbar if you pass an active scrollcontroller to the scrollbar.
-
- 04 Jun, 2019 1 commit
-
- 03 Jun, 2019 1 commit
-
-
Tong Mu authored
- A refactor that moves the semantics declaration from detectors to recognizers to allow custom recognizers to respond to semantic gectures. - Renames all handlers related to semantics from Gesture* to Semantics*.
-
- 31 May, 2019 1 commit
-
-
Michael Goderbauer authored
-
- 25 May, 2019 1 commit
-
-
Chris Bracken authored
Updates documentation and non-public API to use American spellings for consistency with the rest of the codebase. No changes to behaviour... other than how it's spelt.
-
- 20 May, 2019 1 commit
-
- 01 May, 2019 1 commit
-
-
Jonah Williams authored
This reverts commit fea2c7d6.
-
- 30 Apr, 2019 1 commit
-
- 29 Apr, 2019 2 commits
-
-
Jonah Williams authored
This reverts commit 727e7e82.
-
Tong Mu authored
* Callbacks of tap, long press, drag, and double tap GR respond to only primary events. * Add "secondary" callbacks to tap. * Recognizers only compete on events if there are any related callbacks. * Add "kSecondaryButton" constant.
-