https://bugs.kde.org/show_bug.cgi?id=465957
--- Comment #24 from Evert Vorster <[email protected]> --- Thanks for the input. I am already working with libinput to resolve the case of my hardware specifically. But, I feel a point has been missed here. What about hardware that can't or won't be supported by libinput? What about the time that it takes for hardware to be properly supported? You simply *can't* rely on an external library to do the right thing, always. You _need_ to have a catch-all where you can support changing stuff around. Some advanced mode where you can select: This device is NOT a mouse, or that device IS a mouse. Not so much for what input you get from the device, but for how KDE is treating the device, and which options it sets. If KDE does not have this sort of thing, it will just be broken for a lot of people, and leave a bad impression. If you point me at where this code lives I'll vibe-code an example of what I mean... TL;DR: Input is core functionality, there should be fall backs for when things don't perform as expected. -- You are receiving this mail because: You are watching all bug changes.
