On Fri Oct 6 13:01:05 2023 +0000, Rémi Bernon wrote:
Practically, this all means that I can just drop the last commit from
this MR, and perhaps move it to a parallel MR where we can continue to discuss solutions, while we move forward with other things. The rest of this MR doesn't really depend on the last commit, so it would be fine to move forward without it. Yep.
I would deprioritize features like copy/paste, full keymap support,
cross-process rendering (although that would help with some games/launchers/store apps, but is unfortunately quite complex). Yes, I don't think these are critical things to have. Regarding keyboard mapping specifically, I have seen in some branch that you had copied winex11 keyboard layout detection, and I would really like to avoid duplicating that code. I'm trying to get rid of it on the winex11 side, and it's already quite difficult and controversial there, so I was hoping maybe we could do something better in the wayland driver from the start :). Having only US layout support at first would probably be good enough.
@afrantzis I don't know if you are aware of this problem but wine on wayland at least this branch https://gitlab.winehq.org/afrantzis/wine/-/tree/wayland
doesn't support NVIDIA at all it shows a transparent or a black screen and i am pretty sure this is related to wayland not dxvk or anything related since disabling dxvk gives the same transparent or black screen
I builded your branch with https://github.com/lutris/buildbot
I tried both opengl and vulkan backend and I am using bottles to test your wine version