I thought it would be better for there to be an issue, which clearly tracks the wayland blockers.
We can't support pure Wayland sessions for the following reasons:
- wine requires X11:
wine (and lutris/steam by extension) use X11 windows for the games. So, you cannot run GW2 without X11 (or Xwayland) anyway. Maybe in 2025? https://gitlab.winehq.org/wine/wine/-/merge_requests?scope=all&state=opened&search=winewayland
- Wayland doesn't support window positions:
Wayland has no concept of window "position". we cannot get positions of our window or gw2 window. and we cannot set position of our window. And, without those functions, we cannot move the overlay on to gw2 window. Go express your support on https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264 , which is just the first step in getting this working.
- Wayland doesn't provide global cursor position: When our window is "passthrough" (letting mouse clicks hit the window behind us), We are not going to get any mouse events. On X11, we get global cursor position and check if the mouse is on any of our "GUI" areas and decide to disable passthrough feature. But, on Wayland, we cannot get cursor position, and have no idea on when to disable the passthrough feature. Technically, we can use alternate means of doing this, but it would definitely be more like a hack, compared to being a first class feature.
- less demand: Compared to the vast majority of people who will just use
xwayland, very few actually "need" pure wayland support. Should we really be prioritizing this over other features?
I thought it would be better for there to be an issue, which clearly tracks the wayland blockers.
We can't support pure
Waylandsessions for the following reasons:wine(andlutris/steamby extension) useX11windows for the games. So, you cannot runGW2withoutX11(orXwayland) anyway. Maybe in 2025? https://gitlab.winehq.org/wine/wine/-/merge_requests?scope=all&state=opened&search=winewaylandWaylandhas no concept of window "position". we cannot get positions of our window or gw2 window. and we cannot set position of our window. And, without those functions, we cannot move the overlay on to gw2 window. Go express your support on https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/264 , which is just the first step in getting this working.xwayland, very few actually "need"pure waylandsupport. Should we really be prioritizing this over other features?