- 13 Jan, 2016 1 commit
-
-
Eric Seidel authored
Fixes #1213.
-
- 12 Jan, 2016 11 commits
-
-
Adam Barth authored
Also, update callers of deprecated methods.
-
Hans Muller authored
-
Seth Ladd authored
-
Adam Barth authored
We were painting the contents of the RRect clip at the wrong offset. This patch makes RRect match Rect and Path clips. Fixes #1194
-
Eric Seidel authored
Makes it more obvious that flutter analyze takes a long time. @Hixie
-
Ian Hickson authored
If you change the RenderObject tree between frames, you'll assert if you subsequently hit test. So e.g. if you get two button presses back to back, and you mutate the tree synchronously in response to the first one, the second will assert. This adds an onBuild callback to WidgetToRenderBoxAdapter to make it easier to do the updates at the right time, i.e., during widget build. It'll be called whenever you rebuild the WidgetToRenderBoxAdapter itself, so all you have to do to use it is call setState() on whoever is building the WidgetToRenderBoxAdapter.
-
Adam Barth authored
We no longer need to pass bounds to SceneBuilder. Instead, the compositor computes these bounds itself from the RTrees in the SkPictures.
-
Ian Hickson authored
The onHighlightChanged callback was being given "true" every time instead of the actual value.
-
Adam Barth authored
This patch adds ShaderLayer and makes ShaderMask use it. Fixes #1155
-
Adam Barth authored
-
Alex Fandrianto authored
Related: https://github.com/domokit/mojo/issues/614 Flutter can play sounds using this package. However, when Mojo Shell is running Flutter, it lacks the necessary media service. This patch creates a hook to the mojo binary `media_service.mojo`. If Mojo Shell is built with this media service, then it will be able to play sounds when running Flutter.
-
- 11 Jan, 2016 15 commits
-
-
Adam Barth authored
The performance overlay is always drawn using the compositor. We should tell the rest of the system that it's going to make a composited layer. Fixes #1177
-
Adam Barth authored
Previously we used a positional argument for widgets that had multiple children. Now we use a named argument that defaults to an empty list. Fixes #241
-
Ian Hickson authored
-
Adam Barth authored
We use the ScrollDirection for more than just scrolling. Fixes #151
-
Matt Perry authored
-
Adam Barth authored
We don't know how to accuately compute paint bounds in the render tree. Instead, we can rely on the compositor to compute the paint bounds for us if we use OpacityLayer to do our opacity blends. Fixes the shadow when closing the menu in the stocks app.
-
Adam Barth authored
Also, introduce alwaysNeedsCompositing to force the "needs compositing" bit to true without necessarily introducing a ContainerLayer into the layer tree. A future patch will make use of alwaysNeedsCompositing to optimize opacity layers.
-
Ian Hickson authored
-
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.
-
Ian Hickson authored
- Add an option to enable debugPaintSizeEnabled. - Add an option to enable the StatisticsOverlay. - Add support for the StatisticsOverlay in MaterialApp. - Change the layout behaviour of RenderStatisticsBox: - Give it a zero intrinsic width. - Give it an accurate intrinsic height that depends on the flags set. (Also, move the enum to the rendering/ layer from the widgets/ layer to enable this.) - Make the box automatically size itself full-width and the correct height, so that you can actually embed it (though most of the time you'd just put it in a Stack so this doesn't matter as much, really). - Some style nit fixes in statistics_box.dart.
-
Adam Barth authored
When the TabView widget's children change, we don't change the children we give to the PageViewport because we fail to update _items. This patch watches didChangeConfig and updates _items appropriately. Fixes #1134 Fixes #1168
-
Adam Barth authored
Instead of taking a builder and a generic type, we can just take a List<Widget>.
-
Ian Hickson authored
Without this, FlatButton ends up using two RenderConstrainedBoxes back to back for no good reason.
-
Ian Hickson authored
This makes it more consistent with tightFor(), and also makes it easier to tighten both directions at once when you're not sure you will always do so (e.g. if you have a height and width that might be null, and want to tighten whichever ones aren't null).
-
Ian Hickson authored
Also, make dev/update_packages.dart skip directories that have no pubspec.yaml, since firebase/ doesn't have one.
-
- 10 Jan, 2016 3 commits
-
-
Ian Hickson authored
-
Ian Hickson authored
-
Ian Hickson authored
This will allow AnimatedPositioned to reuse all the same logic.
-
- 09 Jan, 2016 3 commits
-
-
Ian Hickson authored
Not sure what I was doing when I wrote this assertion, but I'm pretty sure it's wrong. I'm guessing the change here is what I actually meant to write.
-
Ian Hickson authored
- padding is shown in blue with a darker blue around the child - spacing (empty size boxes or padding) is shown in gray - alignment from a RenderPositionedBox is shown with yellow arrows
-
Adam Barth authored
When I tightened up the layout constraints for the Drawer in the Scaffold, I ended up making the edge swipe detector cover the entire screen. This patch fixes that issue by putting the gesture detector for the edge swipe just around the container with the proper width. We now use a global key to maintain the state across hierarchy changes.
-
- 08 Jan, 2016 7 commits
-
-
Collin Jackson authored
-
-
Hans Muller authored
-
Ian Hickson authored
Change how GridPaper works so that it's easier to plug in anywhere. It now takes a child that it will paint the grid over. It defaults to semi-transparent grid-paper-blue. The line spacing is also more configurable now.
-
Ian Hickson authored
See: https://github.com/flutter/flutter/issues/1080
-
Adam Barth authored
Previously, we triggered a layout (and hence a repaint) when sliding the draw because we gave the draw loose constraints. The drawer uses an Align to move itself to the proper side of the screen, so it can have tight constraints, which makes it a layout boundary. Also, don't trigger a layout just because the Scaffold rebuilds. There isn't any state in the scaffold custom layout, so it doesn't need to repaint just because we created a new instance of the delegate. Finally, add the debugging infrastructure I used to find these issues.
-
Ian Hickson authored
-