- 22 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 16 Nov, 2016 1 commit
-
-
Ian Hickson authored
I used the wrong identifiers here.
-
- 15 Nov, 2016 1 commit
-
-
Ian Hickson authored
See https://github.com/flutter/flutter/pull/6861 This silences all but two of the warnings from https://travis-ci.org/flutter/flutter/builds/176055550 One of the silenced warnings was a genuine code error. Some of the others were correct but there was no way for the analyzer to know, and I worked around them. The remainder are problems with the analyzer, specifically https://github.com/dart-lang/sdk/issues/27827 and https://github.com/dart-lang/sdk/issues/27504.
-
- 28 Oct, 2016 1 commit
-
-
Jason Simmons authored
If a recognizer is interrupted by an exception from a callback, it could be left in an inconsistent state and be unable to process future events
-
- 17 Oct, 2016 1 commit
-
-
Adam Barth authored
Previously, we were nulling out the ArenaEntry in MultiDragPointerState too early, which was prevent MultiDragPointerState from rejecting the gesture in `dispose` if we hadn't accepted by the time the pointer went up. Now we properly reject the gesture, which causes the tap gesture to win during `sweep` in the arena. Also, add a bunch of docs and annotations based on information I learned while studying this issue. Finally, rename a private member of tap recognizer to a name that would have confused me less in my investigation. Fixes #1186
-
- 07 Jun, 2016 1 commit
-
-
Adam Barth authored
We have these details objects for the same reason we now have drag details objects: future extensibility.
-
- 17 May, 2016 1 commit
-
-
Adam Barth authored
-
- 14 Mar, 2016 1 commit
-
-
Hixie authored
-
- 25 Feb, 2016 2 commits
-
-
Adam Barth authored
There's no reason to make clients supply a PointerRounter and a GestureArena when constructing gesture recognizers. These objects are statics and the gesture recognizers can just grab them directly. Also, remove the callback constructor arguments. Almost no code used them. Instead, people seem to prefer using the `..` operator to set callbacks on the recognizers. Removing the arguments removes a bunch of boilerplate.
-
Hixie authored
This allows us to adjust exactly which gestures we're listening for during layout, which I'll use to kill a SizeObserver.
-
- 27 Jan, 2016 1 commit
-
-
Hixie authored
-
- 14 Dec, 2015 1 commit
-
-
Ian Hickson authored
-
- 05 Dec, 2015 1 commit
-
-
Ian Hickson authored
Instead of PointerInputEvent having a "type" field, we now have a different class for each pointer type. This has ripple effects throughout the system. I also did code cleanup in affected files while I was there.
-
- 02 Dec, 2015 1 commit
-
-
Florian Loitsch authored
-
- 13 Nov, 2015 1 commit
-
-
Ian Hickson authored
Make sure to send tapcancel when the primary pointer fails because of slop, even if the gesture won by default. Also, minor cleanup and clarification of an invariant.
-
- 03 Nov, 2015 4 commits
- 27 Oct, 2015 3 commits
-
-
Kris Giesing authored
-
Adam Barth authored
Fixes #1807
-
Adam Barth authored
We don't want to expose these from the gesture package. This patch moves DoubleTapGestureRecognizer into tap.dart so we can make TapTracker and TapGesture private to that file.
-
- 26 Oct, 2015 2 commits
-
-
Kris Giesing authored
Don't use a timeout to cancel tap tracking. Track only one primary pointer and ignore non-primary pointers. Update tests to reflect desired behaviors. Fixes #1779, #1780, #1781.
-
Ian Hickson authored
-
- 23 Oct, 2015 2 commits
-
-
Kris Giesing authored
-
Kris Giesing authored
-
- 20 Oct, 2015 1 commit
-
-
Kris Giesing authored
-
- 13 Oct, 2015 1 commit
-
-
Kris Giesing authored
-
- 10 Oct, 2015 2 commits
-
-
Adam Barth authored
-
Adam Barth authored
-
- 09 Oct, 2015 2 commits
-
-
Kris Giesing authored
-
Hixie authored
Now that you import a top-level file for each layer of the Flutter framework, within the framework we can use relative paths without being worried about the copy/pasta problem we used to have.
-
- 03 Oct, 2015 3 commits
-
-
Adam Barth authored
After this patch, InkWell is driven by gesture recognizers, which lets us cleanly cancel splashes when the user actually scrolls. I've also refactored all the clients of InkWell to use InkWell to detect gestures instead of wrapping InkWell in a GestureDetector. Fixes #1271
-
Adam Barth authored
* Rename GestureTapListener (and friends) To GestureTapCallback to match the other gesture callbacks. * Replace "ensureFoo" pattern with ??= operator.
-
Kris Giesing authored
-
- 17 Sep, 2015 1 commit
-
-
Adam Barth authored
This patch is part of a sequence of patches towards fewer top-level libraries. In this patch, the gesture libraries are combined into one gestures.dart library.
-
- 28 Aug, 2015 2 commits
-
-
Adam Barth authored
This patch replaces the scroll gestures used by Scrollable with ones detected by the ScrollGestureDetector.
-
Adam Barth authored
These gestures use the new gesture detection system.
-