On Wed May 27 10:24:12 2026 +0000, Rémi Bernon wrote:
This sounds interesting but it's a large amount of change and the direction we should take for proper and future-proof DWM support is unclear. It doesn't seem reliable to use the host compositors features as they might not be flexible enough to match Windows requirement, and we might prefer doing the composition ourselves instead. Then you can't add new syscalls if they aren't in native (Windows) dlls, though there are ways around it, especially through the generic NtUserCallHwnd. And then looking at the unusually large amount of documentation, and the world wide trend, I probably have to ask, was this written with help from an LLM? For a few years now I've thought that the future of the virtual desktop should just be a self-contained DWM compositor within an X11, Wayland, or MacOS window. That way the virtual desktop doesn't have to use a different implementation per-platform. It can also function as a place to test the correctness of the DWM implementation before attempting to bring any DWM features outside of the virtual desktop.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/10180#note_141412