hello, thanks for the feedback
i, well, had no wine or win32 experience before writing this, and spent half a day yesterday trying to understand both, and since wayland i know, started there. so, apologies i didn't know much of win32.
Win32 owned windows are a more general concept than xdg_popups
considering this, i do agree subsurfaces make more sense in the general case.
Inversely, some transient windows are not owned, and we need to guess a suitable parent if we want to anchor them to another wayland surface (see, e.g., my WIP branch).
i noticed this on winecfg, where the dropdowns were like that and didn't properly get matched, tried to poke at that today but didn't have much time to find out a way.
some are not (e.g., dialogs) and are better served by another mechanism (e.g., xdg_toplevel parent/child),
was using xdg_dialog thought of for win32 dialogs?
Then I think we will have a clearer view, as a well as a base to compare against, in order to explore how and when to utilize xdg_popups to achieve better integration. How does that sound?
that sounds good.
--
ps: i've also been working on patches to use xdg_decoration to conditionally use server side decorations like the x11drv does, if that's of any interest