On Fri Oct 6 11:12:52 2023 +0000, Alexandros Frantzis wrote:
(cc @erenoit) The linked proposal offers a mechanism to query Wayland surface positions (`get_placement`), which is information we could use to sync in one direction. For the other direction, only just today the scope has expanded to support surface movement hints at arbitrary points after creation, so more in line with what we could be useful for Wine. That being said, I don't think that the overall disposition of the Wayland community to absolute positioning has changed much. In the protocol discussion I am seeing significant pushback, so I wouldn't hold my breath for this (or something similar) landing any time soon. Perhaps a protocol that only implements the `get_placement` part would be more amenable to upstream, and would still provide some benefit to the Wayland driver. Of course, if (and that's a big if) we eventually get a relevant protocol, and which becomes sufficiently widely adopted, I would be happy to use it.
I wasn't really expecting a different answer, but I think it raises the question whether using toplevel surfaces for toplevel Wine windows is the right approach. I don't know whether there are alternatives, but the need for workarounds and heuristics in the Wine driver doesn't sound very appealing.