Felix Schütt

Yes, I migrated the layout system to `stretch`, but I had to change things for performance reasons and there are currently no layout tests. I've fixed the wiki (for a...

@jhwgh1968 The old layout solver had no flexbox tests, and the new layout solver isn't yet finished (hence the blank screen). Just wait. This repository isn't ready yet.

GPU / driver? GLSL 1.20 should be supported if GLSL 1.40 is installed. This is probably a GPU driver bug.

Thanks for reporting, but I don't think I can do much about this atm, way too busy.

Are you on wayland or X11?

I know what the issue is (the window is hidden until the first paint, to prevent flickering, but for some reason the code for actually showing the window never executes),...

@kirillt This should technically be fixed now, but I didn't have the time to verify that it's fixed, could you try again (without the BACKEND=x11 trick)?

The layout is "broken" because of the new layout solver. I tried introducing `display:inline`, but it didn't work out. The screenshots were made using the old layout solver (written October...

- Azul currently renders the output of every window to a regular OpenGL texture ([code here](https://github.com/maps4print/azul/blob/b08882a0e36b3baf3d7096587e948e2117e2573d/azul/app.rs#L1742)). The problem would probably not be "how do I get the output texture", but...

@nico-abram Just an update, but there is now a [headless example](https://github.com/maps4print/azul/blob/d83b0da91352f7c019ed1a1d6e13eedeac8bc880/examples/headless/headless.rs) that shows you how to use azul without webrender (to use just the layout solver, for a custom renderer...