- 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
-
- 09 Sep, 2016 1 commit
-
-
Ian Hickson authored
I did a pass through some of the code cleaning minor things up.
-
- 02 Aug, 2016 1 commit
-
-
Hans Muller authored
-
- 01 Jul, 2016 1 commit
-
-
Adam Barth authored
This patch updates the framework to use the new SemanticAction in semantics.mojom.
-
- 07 Jun, 2016 2 commits
-
-
Adam Barth authored
We have these details objects for the same reason we now have drag details objects: future extensibility.
-
Adam Barth authored
We were trying to unregister the pointer route twice. Now we only unregister it once. Fixes #4341
-
- 03 Jun, 2016 2 commits
-
-
Adam Barth authored
I changed the behavior late in the code review but didn't update this dartdoc.
-
Adam Barth authored
Previously we supplied individual parameters to the various drag and pan callbacks. However, that approach isn't extensible because each new parameter is a breaking change to the API. This patch makes a one-time breaking change to the API to provide a "details" object that we can extend over time as we need to expose more information. The first planned extension is adding enough information to accurately produce an overscroll glow on Android.
-
- 18 May, 2016 1 commit
-
-
Adam Barth authored
Also, make some previously private classes public for better documentation.
-
- 17 May, 2016 2 commits
-
-
Adam Barth authored
-
Adam Barth authored
Also, add some missing docs to http.dart and widgets.dart.
-
- 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 Mar, 2016 1 commit
-
-
Hans Muller authored
-
- 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
-
- 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.
-
- 14 Feb, 2016 1 commit
-
-
Adam Barth authored
We were using an Offset, which represented pixels/second, but it wasn't clear to clients whether that was pixels/ms. Now we use a Velocity class that is explict about the units. Fixes #1510 Fixes #785
-
- 14 Dec, 2015 1 commit
-
-
Ian Hickson authored
-
- 09 Dec, 2015 1 commit
-
-
Hans Muller authored
-
- 05 Dec, 2015 2 commits
-
-
Ian Hickson authored
-
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.
-
- 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.
-
- 02 Nov, 2015 1 commit
-
-
Kris Giesing authored
-
- 27 Oct, 2015 1 commit
-
-
Adam Barth authored
Fixes #1807
-
- 23 Oct, 2015 1 commit
-
-
Adam Barth authored
Now we use one velocity tracker per pointer. Path by Kris Giesing. Fixes #1704
-
- 13 Oct, 2015 1 commit
-
-
Kris Giesing authored
-
- 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.
-
- 17 Sep, 2015 3 commits
-
-
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.
-
Collin Jackson authored
-
Collin Jackson authored
Conflicts: sky/packages/sky/lib/gestures/drag.dart
-
- 16 Sep, 2015 3 commits
-
-
Collin Jackson authored
-
Collin Jackson authored
Conflicts: sky/packages/sky/lib/gestures/drag.dart
-
Adam Barth authored
This fixes an issue in the stocks app in horizontal mode where you could both scroll and drag the drawer at the same time.
-
- 11 Sep, 2015 2 commits
-
-
Adam Barth authored
The gesture is now called "drag". The library name should match.
-
Hans Muller authored
Dismissable now only depends on GestureDetector. Added a unit test that verifies that issue #1068 has been fixed. It's commented out for now. Cleaned up VelocityTracker.cc et al a little.
-