Wayland support

[fgaz]

When flitter is run under wayland (sway in my case), input is not recognized. The latest GNOME and KDE environments also default to wayland and should exhibit the same issue.

[fgaz]

In a lot of upstream issues this is labeled as impossible. However, that is outdated, as we have org.freedesktop.portal.GlobalShortcuts now.

Edit: I opened ostrosco/device_query#86
Edit2: Maybe it makes more sense to use https://docs.rs/ashpd/0.9.1/ashpd/desktop/global_shortcuts/index.html directly, to avoid polling

[alexozer]

Oh man, I was hoping to avoid async Rust! Maybe it's easy to slot it in by polling futures though?

[BuyMyMojo]

Any updates on this issue?

[alexozer]

Seems like GNOME hasn't finished implementing org.freedesktop.portal.GlobalShortcuts. Since Wayland seems lacking feature parity with X11 as ever, I might be willing to hack something in to read inputs at the keycode layer (requiring sudo) like Input Remapper.

[Opposite34]

Seems like GNOME hasn't finished implementing org.freedesktop.portal.GlobalShortcuts. Since Wayland seems lacking feature parity with X11 as ever, I might be willing to hack something in to read inputs at the keycode layer (requiring sudo) like Input Remapper.

https://gitlab.gnome.org/GNOME/xdg-desktop-portal-gnome/-/merge_requests/208 it's there in GNOME now supposedly. I have not looked into it though.

[laundmo]

I've implemented global input in my Rust app using the evdev crate, which utilizes the kernel system of the same name. This works completely independent of compositor or desktop, since it hooks far deeper than that. The main downside is that it requires that the user runnig it has the input group, or otherwise has access to /dev/input. It also bypasses keyboard layout configuration, recieving raw keycodes instead.

But it would be a way to not need any specific wayland protocol or desktop portal.