- 07 Jul, 2016 1 commit
-
-
Adam Barth authored
Fixes #4761
-
- 07 Jun, 2016 1 commit
-
-
Adam Barth authored
We were trying to unregister the pointer route twice. Now we only unregister it once. Fixes #4341
-
- 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.
-
- 18 May, 2016 1 commit
-
-
Adam Barth authored
Also, make some previously private classes public for better documentation.
-
- 17 May, 2016 1 commit
-
-
Adam Barth authored
-
- 26 Apr, 2016 1 commit
-
-
Adam Barth authored
Wait until the end of the microtask to tell gesture recognizers that they've won in the gesture arena. This lets recognizers dispose reject themselves at arbitrary times without triggering gestures in awkward call stacks. Fixes #3183
-
- 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.
-
- 15 Mar, 2016 1 commit
-
-
Adam Barth authored
The problem was we were using a tap gesture to stop the motion of the drawer and a drag gesture to settle it. That can cause a broken lifecycle. Now we use a single drag recognizer to drive the whole lifecycle. Fixes #775 Fixes #1276
-
- 14 Mar, 2016 1 commit
-
-
Hixie authored
-
- 12 Mar, 2016 1 commit
-
-
Adam Barth authored
Also, change the keys to be explicitly pointer ids. Fixes #202
-
- 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.
-
- 24 Jan, 2016 1 commit
-
-
Ian Hickson authored
-
- 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.
-
- 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.
-
- 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 1 commit
-
-
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.
-
- 03 Nov, 2015 1 commit
-
-
Hixie authored
Turns out there were no uses of GestureArenaMember other than those that use DisposableArenaMember.
-
- 13 Oct, 2015 1 commit
-
-
Kris Giesing authored
-
- 12 Oct, 2015 1 commit
-
-
Hixie authored
Add type annotations in many places. Fix some identifiers to have more lint-satisfying names. Make all operator==s consistent in style. Reorder some functions for consistency. Make ParentData no longer dynamic, and fix all the code around that.
-
- 10 Oct, 2015 2 commits
-
-
Adam Barth authored
-
Adam Barth authored
-
- 09 Oct, 2015 1 commit
-
-
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 1 commit
-
-
Kris Giesing authored
-
- 02 Oct, 2015 1 commit
-
-
Adam Barth authored
Fixes #1320
-
- 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.
-
- 10 Sep, 2015 1 commit
-
-
Adam Barth authored
That way the fling engages in the same direction as the scroll. For example, if you have a horizontal scroll nested inside a vertical scroll, the fling will take place in the same direction as the scroll.
-
- 08 Sep, 2015 1 commit
-
-
Adam Barth authored
These files really belong on other libraries.
-
- 30 Aug, 2015 1 commit
-
-
Adam Barth authored
If there are no other gestures in the arena, we should kick off the scroll gesture right away. This change pulled a refactoring of how we dispatch events to Widgets. Now we dispatch events to Widgets interleaved with their associated RenderObjects. (Previously we dispatched to all of the RenderObjects first.)
-
- 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.
-