- 08 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
Covers lib/ in package:flutter.
-
- 27 May, 2016 1 commit
-
-
Adam Barth authored
We'll use this functionality to implement some subtle behaviors for tooltips.
-
- 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 Apr, 2016 1 commit
-
-
Ian Hickson authored
We're getting back to the point where we have a bunch of foundation APIs and it's getting confusing having them mixed with services/.
-
- 12 Apr, 2016 1 commit
-
-
Ian Hickson authored
This also shrinks the width of the error messages a bit because now that we use 'package:' URLs the stacks are a bit narrower.
-
- 03 Apr, 2016 1 commit
-
-
Ian Hickson authored
-
- 02 Apr, 2016 1 commit
-
-
Ian Hickson authored
- Create a FlutterErrorDetails struct-like class that describes an exception along with more details that aren't in the exception, like where it was caught and what was going on when it was caught. - Provide a FlutterError static API for handling these objects: - FlutterError.onError which is called whenever Flutter catches an error. - FlutterError.reportError() which handles an error. - FlutterError.dumpErrorToConsole() which is the default behavior for onError. - Removes all the existing exception handler callbacks. - Replaces all the existing places that described exceptions using debugPrint with calls to FlutterError.reportError(). - Extend lockState() to also catch exceptions, so that we catch exceptions that happen during finalizers. - Make the test framework catch errors and treat them as failures. - Provide a mechanism to override this behavior in the test framework. - Make the tests that used to depend on the exception handler callbacks use this new mechanism. - Make pump() also support the phase argument. - Improve some tests using these new features. Fixes #2356, #2988, #2985, #2220.
-
- 11 Jan, 2016 1 commit
-
-
Adam Barth authored
The pointer router was using an iteration pattern that always delivers handleEvent calls even if you remove a route during the iteration. That's awkward to program against and causes trouble for the double-tap gesture. This patch switches PointerRouter to using a re-entrant iteration pattern that supports removing routes (but not adding routes) during the iteration.
-
- 07 Jan, 2016 1 commit
-
-
Ian Hickson authored
- make them all have the same style - make them all include the stack trace last - make them all stop printing if their callback is set (if appropriate, they don't yet all have callbacks)
-
- 15 Dec, 2015 1 commit
-
-
Hixie authored
If we don't catch these exceptions, we get confused about what's going on with the pointers, and the app basically stops working.
-
- 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 Oct, 2015 2 commits
-
-
Kris Giesing authored
-
Kris Giesing authored
-
- 10 Oct, 2015 2 commits
-
-
Adam Barth authored
-
Adam Barth 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.
-
- 08 Sep, 2015 1 commit
-
-
Adam Barth authored
These files really belong on other libraries.
-
- 30 Aug, 2015 2 commits
-
-
Adam Barth authored
-
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.)
-
- 27 Aug, 2015 1 commit
-
-
Adam Barth authored
This patch is the first step towards implementing gestures. The pointer router allows the gesture detectors to hook in at the end of the pointer event propagation chain. Related to #145
-