Todd Volkert wrote:
> I'll add that due to the nature of layout, a component might be asked
> for its preferred size N times in one event loop as each component in
> its ancestry lays itself out, so caching it especially optimizes this
> case. In my tests, caching this reduced layout time by almost two
> orders of magnitude (from ~100ms to ~1ms).
>
It might be handy to document things like this in the code - it's not at
all obvious from a cursory examination, and will get future generations
of Pivot coders up to speed much faster.
