Originally posted by jacob
View Post
It was a "We've given you more than enough time. Now we're going to fix it" response to a laundry list of problems.
Some of them were rooted in X11 not synchronizing with the application for what a newly resized window should look like, so you'd see flickers of messed-up rendering as the toolkit raced with X to get the layout revised before the next scan-out. Hence "every frame is perfect" being one of the design statements for Wayland.
Others were related to the X11 event system not supporting transforms. Reinventing everything below the level of top-level window is what allows Qt to implement things like clicking on transformed buttons.
(And that support for transforms was one of the big things that GTK+ users lamented Qt being ahead of them on at the time.)
Comment