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.
Introduces a new Widget that lays its child out, but does not render it.
Also, moves RenderOverflowBox to its own file since it has nothing to do
with proxy box really.
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.
