Consolatis
Consolatis
Where do these `wl_keyboard_listener::{key,modifiers}` come from? `WAYLAND_DEBUG` from wlfreerdp or labwc internal callbacks?
Might be related: https://github.com/labwc/labwc/pull/1226#pullrequestreview-1726120212
> I'm just printf'ed this events in wlfreerdp directly. Hm, in that case it is indeed weird that there are multiple wl_keyboard_modifier events, there should only be one for each...
I had a quick read through the code and although I miss some context as for how this works together (need to read the protocols and wlroots headers) I have...
I like the general approach by @tokyo4j above as it basically just interprets the touch down event on the window the same as a mouse click by calling the same...
Thanks! Should be fixed by - #1550
I like the general idea, we do have to update `src/input/cursor.c` as well though, currently we just give any layer surface focus on click. We should likely have a single...
> > I like the general idea, we do have to update `src/input/cursor.c` as well though, currently we just give any layer surface focus on click. We should likely have...
There seems to be something going on with wlroots 0.17 and virtualized GPU drivers. Maybe some env vars from https://gitlab.freedesktop.org/wlroots/wlroots/-/blob/master/docs/env_vars.md may help? E.g. `WLR_EGL_NO_MODIFIERS=1` and / or `WLR_DRM_NO_MODIFIERS=1` and /...
Tracked in - #1829