- 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.
-
- 01 Jun, 2016 1 commit
-
-
Adam Barth authored
This patch starts using the mustCallSuper annotation for several of the key lifecycle callbacks in the framework. I haven't added it to didUpdateConfig because there are a large number of non-compliant overrides. We should discuss whether we want to use it there.
-
- 25 May, 2016 1 commit
-
-
Adam Barth authored
For consistency. Fixes #4142
-
- 17 May, 2016 1 commit
-
-
Adam Barth authored
-
- 22 Apr, 2016 1 commit
-
-
Ian Hickson authored
The old names were getting silly and started stepping on valuable namespace. The new names are consistent and clear.
-
- 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.
-
- 11 Feb, 2016 1 commit
-
-
Hixie authored
This lets it cooperate with other gestures like tap. The way I implemented this was to refactor the entire Draggable gesture logic to use a new kind of gesture detector called MultiDragGestureRecognizer. It works a bit like MultiTapGestureRecognizer but for drags. Also some tweaks to the velocity estimator.
-
- 14 Dec, 2015 1 commit
-
-
Ian Hickson authored
-
- 10 Dec, 2015 1 commit
-
-
Florian Loitsch 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.
-
- 05 Nov, 2015 1 commit
-
-
Hixie authored
Draggable is now itself a gesture arena member. This means it won't conflict with other gesture recognisers in the same path. This also allows variants of Draggable that are triggered by other gestures. Also, some cleanup of DoubleTapGestureRecognizer, GestureDetector, and PrimaryPointerGestureRecognizer. Also, make MultiTapGestureRecognizer support a timeout for longpress. Also, make Draggable data be typed. Also, hide warnings about constructor warnings for now. Analyzer doesn't support them yet. (Have to do this on a per-line basis) Directions for future research: - animating the avatar (enter/exit transitions) - interaction with the navigator (canceling a drag on page navigation, etc) - double-tap draggable
-
- 04 Nov, 2015 2 commits
-
-
Hixie authored
Make all the *GestureRecognizer classes inherit from a class called GestureRecognizer. Give the old GestureRecognizer a name that is more precise about its purpose. Remove the members of GestureArenaMember that aren't used by GestureArenas.
-
Hixie authored
Document the Gesture Detector constants. Remove kEdgeSlop since it's obsolete on Android. Add a test that verifies that when the first tap is canceled, the second tap can become the first tap of a subsequent two-tap sequence.
-
- 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.
-