ping

Be sure to sandbox __gc as it runs outside of the debug hooks that limit execution time

You can't avoid calling layout on children, however, the framework does implement optimizations that short-circuit it for you. If the constraints passed to a child are the same as in...

Its not possible to read the offset of descendants because there is no way to guarantee that a child changing size will re-layout its grandparent. Do you have a visual...

Is the end goal to draw that line between them? You can do that entirely in a painter, it's generally safe to access RenderObjects during the paint phase and the...

The framework makes very strong assumptions about how data is passed between RenderObjects during layout, specifically, only constraints can go down and only geometry can go up, any communication outside...

The only significant cost to GlobalKey is when its used to reparent the child widget, accessing it alone is usually fine. You shouldn't use it to access descendants during layout...

Also the gist I posted above implements what I thought you wanted to do, and it doesn't require subclassing RenderObject.

The gist doesn't rely on the size of the child being known at build time, only `OverflowingChild.padding` Do you have a diagram or example of the layout you are trying...

Hey, sorry for the late response! Unfortunately, boxy can't circumvent these errors during layout I think a possible workaround in your case is to do this scroll adjustment outside of...

When the ImageProvider completes, it notifies every listener at the same time, so the scroll adjustment should happen on the same frame as the image being painted for the first...