Make Radio widgets take a type that describes the type of their value,
so that you can catch when you use the wrong value.
Standardise on ValueChanged<Foo> instead of having a FooValueChanged
for every value of Foo.
Implements a mode that highlights RenderBoxes while events are being
routed through them.
Also, moves the size painting to after paint, so that opaque boxes
don't obscure the debugging lines.
If the text is empty, the IME may call deleteSurroundingText(1, 0) if the user
hits the delete key. The selection should remain at position 0 if this
happens.
The NewTextPainter is still disabled by default. A future patch will flip the
flag to enable it.
This patch uses a new approach to writing bindings by encoding data into array
buffers. This approach is more efficient than the existing IDL based approach.
If this works out well, we should convert our other performance-sensitive
interfaces to this approach in future patches.
The magic for updating DebugSize's knowledge about whether it was
allowed to be used by the parent or not previously failed to correctly
deal with sizedByParent.
By default now heroes won't animate if they don't find a matching hero
on the target page. You can make them animate by setting 'alwaysAnimate:
true' on the Hero constructor.
This grid makes it significantly easier to track down errors when you're
looking at coordinates in a render tree dump and want to see if they're
what you expect or if they're wildly away from the right location.
These new PerformanceView classes are transforms over PerformanceViews.
The first is a cheap way to tell code that expects a performance to not
animate after all, and the other is a way to replace a view of a
performance going in one direction with a view of a performance going in
the other direction.
See also https://github.com/flutter/engine/issues/1708
Assert at build time that PageRoute route builders do not return null
widget trees.
Also very minor new code comments and code reorg to help make the heroes
patch easier to review.
(These are changes that are unrelated to Heroes but that were part of
the Heroes patch.)
The 0.2.1 release of the mojo package isn't actually compatible with Flutter
despite claiming to be a minor release. The real fix is to make Flutter
compatible with that release, but there are several yak shaves involved.
