maarvin

> * Some of the ugly warts that I _just_ got rid of are returning (`FillFlowContainer.ForceNewRow`), and new ones are appearing (what is `OnLayoutComputed()` even for? signature looks terrible, not...

> As stated does this even need to be a flag? Maybe we can just force-hardcode this behaviour? The original thought behind making it a flag was to make sure...

> Should be changed to a per-frame implementation because right now it is objectively visually wrong – each time autosize changes the duration and easing is rest causing jerkiness. Kinda...

> I'd rather not have a second completely parallel easing system existing in the game, so that one is a NAK as far as I'm personally concerned. No surprise there,...

Test failure was caused by the `didInitialAutoSize` flag only being set once autoSize has been applied at least once, which will also skip it if you enable AutoSize soome time...

> Yes, it would have to go, and be replaced with a single value that adjusts how the continuous damping is applied. There's no really good way of doing an...

> OP is missing discussion of performance of this, which I'd expect to see given reliance on buffered containers which we have found to be rather expensive (especially in terms...

I managed to get rid of most of the framebuffers. I made a `BackdropBlurPath` drawable which uses only one extra framebuffer per path/slider (before it was 3 extra) . If...

If the blur shader in particular is of concern, I think it's probably best if I use 2 lowres buffers and only do the blending in the final pass so...

With the second blur pass being at a lower resolution too now, assuming 25% resolution and 16px blur sigma it should be doing 5 texture samples per pixel for each...