Open chris-y opened 2 months ago
There are two backends in lan-mouse in question here:
The wlr desktop portal does not implement the InputCapture portal yet: https://github.com/labwc/labwc/issues/1263 I've been thinking about writing a libei "bridge" as described in the linked issue and move it out of lan-mouse but that is basically what the layer-shell backend does:
labwc does not implement keyboard-shortcut-inhibit-unstable-v1, which is required for the layer-shell backend to pass keyboard shortcuts that would otherwise be handled by labwc itself: https://github.com/labwc/labwc/issues/1046
Labwc is the first compositor I've come across so far that does not implement this protocol, which is why it has been a hard dependency so far.
Their reasoning as to not implementing it sounds valid to me. Making the protocol a soft dependency for lan-mouse would enable ToggleKeybinds as a workaround.
Automatically toggling this would however require manual action or could maybe be done through an enter_hook
.
Maybe this is a compelling reason for labwc to implement the protocol ;)
Just tested this and it seems like the layer-shell implementation in labwc does not correctly interact with pointer-constraints right now. I will see if I can write a patch for that.
Aside from that, a "leave" hook would probably be needed for the ToggleKeybinds workaround.
I am trying to run lan-mouse on a Raspberry Pi with labwc (I also tried Wayfire), and it is not working. I installed with cargo as per the instructions.
I guess I'm missing something. I checked xdg-desktop-portal was installed.