https://bugs.winehq.org/show_bug.cgi?id=58032
--- Comment #2 from Sergio Callegari scallegari@arces.unibo.it --- @mata
that's configured in the registry via: HKCU\Software\Wine\Drivers\Graphics = "x11,wayland"
Thanks, that's quite nice to know!
for example this is what I've accumulated in my .profile:
export QT_QPA_PLATFORM="wayland;xcb" export GDK_BACKEND="wayland,x11" export SDL_VIDEODRIVER="wayland,x11" export MOZ_ENABLE_WAYLAND=1 export ELECTRON_OZONE_PLATFORM_HINT=auto export GVIM_ENABLE_WAYLAND=1
Almost the same here. Incidentally, this is one of the things that I totally think that the wayland process got wrong: 1000 ways to do the same thing, one for each application, toolkit, whatever. It is OK to have a config variable for each toolkit/application, but that should be only to override a more general setting. And the latter is unfortunately lacking.
However, watching XDG_SESSION_TYPE seems to be assuming the role of a standard for a hint: if the session type is wayland and your application is capable of doing wayland properly, then wayland should probably be preferred. In the case of wine, I think that `HKCU\Software\Wine\Drivers\Graphics` should probably not take just an ordered list of display types, but also 'auto', standing for 'follow the session type', being the default.
IMHO the current situation is somehow unoptimal, because the fact that wine supports wayland becomes hard to discover. Most linux users will have DISPLAY set (because of apps needing Xwayland). With it wine is always started in X11 mode and people (like me!) keep thinking that wine cannot do wayland until they suffer so much about scaling that they discover the old wine-wayland project, they wonder why it does not exist any more, etc. Furthermore, the current status (X11 by default basically) might lead to wayland support remaining with little testing.