- 22 Mar, 2018 1 commit
-
-
Greg Spencer authored
-
- 21 Sep, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 05 Jun, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 02 Jun, 2017 1 commit
-
-
Ian Hickson authored
This prevents some of our mixins from being subclassed. Also, move mixins to using 'extends' instead of 'implements' for future compatibility with Dart changes. Also, rename a class that had Mixin in the name but was not a mixin.
-
- 05 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 12 Apr, 2017 1 commit
-
-
Ian Hickson authored
* Manually fix every use of Point.x and Point.y Some of these were moved to dx/dy, but not all. * Manually convert uses of the old gradient API * Remove old reference to Point. * Mechanical changes I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\bPoint[.]origin\b/Offset.zero/g' git ls-files -z | xargs -0 sed -i 's/\bPoint[.]lerp\b/Offset.lerp/g' git ls-files -z | xargs -0 sed -i 's/\bnew Point\b/new Offset/g' git ls-files -z | xargs -0 sed -i 's/\bconst Point\b/const Offset/g' git ls-files -z | xargs -0 sed -i 's/\bstatic Point /static Offset /g' git ls-files -z | xargs -0 sed -i 's/\bfinal Point /final Offset /g' git ls-files -z | xargs -0 sed -i 's/^\( *\)Point /\1Offset /g' git ls-files -z | xargs -0 sed -i 's/ui[.]Point\b/ui.Offset/g' git ls-files -z | xargs -0 sed -i 's/(Point\b/(Offset/g' git ls-files -z | xargs -0 sed -i 's/\([[{,]\) Point\b/\1 Offset/g' git ls-files -z | xargs -0 sed -i 's/@required Point\b/@required Offset/g' git ls-files -z | xargs -0 sed -i 's/<Point>/<Offset>/g' git ls-files -z | xargs -0 sed -i 's/[.]toOffset()//g' git ls-files -z | xargs -0 sed -i 's/[.]toPoint()//g' git ls-files -z | xargs -0 sed -i 's/\bshow Point, /show /g' git ls-files -z | xargs -0 sed -i 's/\bshow Point;/show Offset;/g' * Mechanical changes - dartdocs I applied the following at the root of the Flutter repository: git ls-files -z | xargs -0 sed -i 's/\ba \[Point\]/an [Offset]/g' git ls-files -z | xargs -0 sed -i 's/\[Point\]/[Offset]/g' * Further improvements and a test * Fix minor errors from rebasing... * Roll engine
-
- 31 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
* add @required when there's an assert not null * address review comments
-
- 10 Mar, 2017 2 commits
-
-
Alexandre Ardhuin authored
-
Alexandre Ardhuin authored
-
- 08 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 21 Feb, 2017 1 commit
-
-
Alexandre Ardhuin authored
Fixes #7734
-
- 23 Nov, 2016 1 commit
-
-
Adam Barth authored
Fixes #5695
-
- 19 Nov, 2016 1 commit
-
-
Ian Hickson authored
-
- 07 Oct, 2016 1 commit
-
-
Adam Barth authored
This patch adds `@checked` everywhere is needed to remove the `strong_mode_invalid_method_override` strong mode error.
-
- 08 Jun, 2016 1 commit
-
-
Ian Hickson authored
Also, make sure that the parent is notified when they change. Fixes #2298
-
- 31 May, 2016 1 commit
-
-
Ian Hickson authored
-
- 27 May, 2016 1 commit
-
-
Adam Barth authored
There are still many more left before rendering.dart is complete.
-
- 25 May, 2016 1 commit
-
-
Adam Barth authored
For consistency. Fixes #4142
-
- 12 May, 2016 1 commit
-
-
pq authored
It's safe to remove the unneeded `void`s from setters since the blocking issues in the `always_declare_return_types` lint have been fixed (https://github.com/dart-lang/linter/). We can also safely flip the bit on `avoid_return_types_on_setters`.
-
- 11 Apr, 2016 1 commit
-
-
Ian Hickson authored
I ran into a case where I was setting minHeight=∞ and then calling layout() with that constraint, which is all kinds of bad. To try to catch this earlier, this patch now provides a way to catch constraints that are requiring infinite values. We don't _always_ check this because there are valid uses for BoxConstraints.biggest, e.g. as an additionalConstraint.
-
- 03 Apr, 2016 1 commit
-
-
Ian Hickson authored
-
- 18 Mar, 2016 1 commit
-
-
Hixie authored
-
- 14 Mar, 2016 1 commit
-
-
Hixie authored
-
- 12 Mar, 2016 2 commits
-
-
Adam Barth authored
Fixes #1482
-
Adam Barth authored
Fixes #459
-
- 08 Mar, 2016 1 commit
-
-
Adam Barth authored
The getSize function from MultiChildLayoutDelegate might depend on information other than the incomming constraints. Fixes #2077
-
- 06 Mar, 2016 1 commit
-
-
Ian Hickson authored
Fixes https://github.com/flutter/flutter/issues/2403 I have an e-mail ready to send to flutter-dev about this.
-
- 03 Mar, 2016 1 commit
-
-
Hixie authored
-
- 10 Feb, 2016 1 commit
-
-
Hixie authored
The asserting will continue until morale improves! * Convert all assert(*.isNormalized) checks to use the new debugAssertIsNormalized technology. * Convert CustomMultiChildLayout to use the new RenderingError technology to greatly improve the detail in errors you get when writing CustomMultiChildLayout delegates. * Add BoxConstraints.copyWith(). * Indent the descendants in the rendering exception data dump so that when you have multiple children it's clearer what's going on.
-
- 09 Feb, 2016 1 commit
-
-
Adam Barth authored
There aren't any clients anymore. Fixes #1684
-
- 14 Jan, 2016 1 commit
-
-
Hixie authored
Introduces a new Tooltip class. Adds support for tooltips to IconButton and Scaffold. Adds some tooltips to various demos. Also some tweaks to stack.dart that I made before I decided not to go down a "CustomPositioned" route.
-
- 08 Jan, 2016 1 commit
-
-
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.
-
- 02 Jan, 2016 1 commit
-
-
Adam Barth authored
Previously we used Position, which makes it harder to accumulate offsets when walking the render tree.
-
- 15 Dec, 2015 1 commit
-
-
Hans Muller authored
CustomMultiChildLayout and CustomOneChildLayout now use their delegate's shouldRelayout() method instead of a "token" to decide if layout is needed. MultiChildLayoutDelegate and OnChildLayoutDelegate are now expected to be stateless, i.e. they'll typically be built each time their custom layout widget is built. If the identical layout delegate is provided to a new custom layout, layout will not happen. Revised the bottom sheet implementation per the new custom layout classes. Removed a SizeObserver. Fixes #899
-
- 10 Dec, 2015 1 commit
-
-
Adam Barth authored
-
- 09 Dec, 2015 1 commit
-
-
Ian Hickson authored
Add BoxConstraints.isNormalized feature. Use this feature in asserts in all the intrinsic dimension methods, in various relevant BoxConstraints methods, and in layout(). Wrap the _DebugSize logic in BoxConstraints.constrain() in an assert block to avoid a branch in release mode. Remove the logic in BoxConstraints.isSatisfiedBy() that dealt with non-normalized values. Add BoxConstraints.normalize(). Make RenderCustomOneChildLayoutBox.performLayout() only set parentUsesSize on the child if the constraints aren't tight.
-
- 07 Dec, 2015 2 commits
-
-
Adam Barth authored
These docs are largely duplicated from the cooresponding rendering classes. I'm not sure how we can avoid repeating ourselves.
-
Adam Barth authored
Add some missing functionality to ParentData subclasses. Fixes #474
-
- 04 Dec, 2015 1 commit
-
-
Adam Barth authored
Fixes #692 Fixes #690
-
- 13 Nov, 2015 1 commit
-
-
Adam Barth authored
Prior to this patch, MultiChildLayoutDelegate couldn't be re-entered because it cleared _idToChild when unwinding its stack. Now we restore the previous value of _idToChild when we unwind.
-