https://bugs.kde.org/show_bug.cgi?id=328987
--- Comment #47 from Darren Anderson <dar...@darrenanderson.dev> --- Did a bit more digging into this, and it seems non-trivial. As of now, KWin receives input from "backends", of which there are several (Wayland, X11, libinput etc). It seems like gamepads exist outside of this usual architecture, as the input would come from the gamepad device itself, rather than via X11, Wayland, libinput etc. Not the nicest solution ever, but I wonder if we might get around this by adding the gamepad read functionality to the base `InputDevice` class? That way it would work across multiple backends, even if it is a bit of a deviation from the current design. -- You are receiving this mail because: You are watching all bug changes.
