https://bugs.kde.org/show_bug.cgi?id=509613
--- Comment #3 from Joshua Goins <[email protected]> --- > I'm not sure of the distinction; should the ideal tablet show up as a > *single* libinput device? I (naively?) expected at least the pen and the pad > buttons to be distinct devices. To be clear in case of misreading, the device > that sends events in response to the pad's buttons *does* show up in libinput > list-devices (it's just one of four with "Huion" in the name). No, there's no limitation in that aspect - because KWin will group it as a single device for us. The problem is that your device is not truly a tablet pad device, it's a keyboard :-) (Aka, it's emulating a keyboard.) For Huion there's a tool somewhere I believe that switches it from keyboard-emulation mode to something we can actually use, but that's something you'll have to figure out for your model of tablet. > If this is an intended restriction in how the module works, is there anywhere > that I could focus on to amalgamating the separate devices into a single one > so that the tablet can work with KDE's paradigm? See above. -- You are receiving this mail because: You are watching all bug changes.
