hikari wayland compositor (https://hikari.acmelabs.space)
#40wlroots 0.15.x: Mouse input going to the wrong views
An issue I noticed with hikari 2.3.3 and the update for wlroots 0.15.x.
Luckily I noticed it until now with Steam and GIMP.
With steam, when a game is launched, the mouse interactions do stuff with the actual steam program instead of the game, even with CSA+g. Move it away from the steam window and it works, until the mouse is over the window again. Even if steam and the game are on separate workspaces.
And that also applies for GIMP. If using the multi window modus, every window of gimp is "stealing" the mouse input. Even worse, it interacts with other apps. In this case with thunar (another GTK3 app). If there is another GIMP or thunar window directly behind the current active gimp window, the mouse button interactions will go to one of these. Symptoms like, not able to confirm actions, working on the wrong picture, moving files instead of marking an area in a picture. Pushing views to another workspace doesn't help.
Some kind of ordering issue? From parent to children?
Is it something which could be fixed with the introduction of the wlroots scene-graph API?
As discussed on matrix channel this https://github.com/riverwm/river/commit/e16eabd9282e77c89e47874838443fb34150b56d resolves this issue.
"summer23: Yeah, of course. At line 308 before the end of function i added "wlr_xwayland_surface_restack(xwayland_surface, NULL, XCB_STACK_MODE_ABOVE)". Without quotes, of course."
I have submitted a patch https://hub.darcs.net/holycow/hikari/patch/de3817572a6c3ba5b51614fe31151d2c63fe1fd4
Great. Build a package with your patch applied and will test it soon.
But as far as I understand, this will only help with programs that run via xwayland? As I'm pretty sure the similar/same issue I'm seeing with some other apps are wayland native.
Or is there some synergy at work? Well, I will see what happens tomorrow, but I'm curious :DI'm pleasantly surprised, that this patch helps also with the case with GTK (and QT) apps. Thank you for looking into it holycow.
But I'm bit puzzled as to why it helped in the case with natively on wayland running apps? Or they don't and I assumed it but my setup misses something. Need to look further into it.Well, with this patch applied the case seems to be solved. I let the issue stay open until this change gets included with this repo :)
