- 23 Nov, 2015 1 commit
-
-
Adam Barth authored
This package contains WidgetTester, which is very useful when writing tests for widgets.
-
- 16 Nov, 2015 1 commit
-
-
Hixie authored
- force the time dilation to 1.0 for the Widget tests, so that a local change doesn't break all the tests during development. - add missing license block to all the files. - set ui.window.onBeginFrame to null when you use WidgetTester, so that the engine doesn't trigger any confusing frames after our fake frames.
-
- 19 Oct, 2015 1 commit
-
-
Hixie authored
Provide a way to schedule a callback for immediately after the current frame has been sent to the GPU thread. This is useful for times where you want to immediately schedule yourself for another build or layout because, for instance, you just displayed frame zero of an animation and you want to use the metrics from that layout to set up the actual animation to begin immediately, such that the very next frame is frame 1.
-
- 10 Oct, 2015 1 commit
-
-
Adam Barth authored
-
- 05 Oct, 2015 1 commit
-
-
Hixie authored
Focus.at() and company should be on Focus, not FocusState. _notifyDescendants() was using the wrong runtimeType. Let InheritedWidget update the descendants during build. When you setState() during build, assert that you're not markNeedsBuild()ing someone who isn't a descendant. Typo in Widget.toString().
-
- 01 Oct, 2015 3 commits
-
-
Adam Barth authored
Fixes #1084
-
Adam Barth authored
-
Adam Barth authored
Now that we've ported all the widget tests to fn3, we don't need a separate fn3 directory.
-
- 30 Sep, 2015 1 commit
-
-
Adam Barth authored
This argument isn't needed anymore now that State has a getter for context.
-
- 28 Sep, 2015 1 commit
-
-
Adam Barth authored
This patch makes a number of changes: 1) buildDirtyComponents now prevents all calls to setState, not just those higher in the tree. This change is necessary for consistency with MixedViewport and HomogeneousViewport because those widgets already build subwidgets with that restriction. If the "normal" build didn't enforce that rule, then some widgets would break when put inside a mixed or homogeneous viewport. 2) We now notify global key listeners in a microtask after beginFrame. That means setState is legal in these callbacks and that we'll produce another frame if someone calls setState in such a callback.
-