https://bugs.kde.org/show_bug.cgi?id=450874
--- Comment #4 from Naomi Calabretta <tony0000...@gmail.com> --- (In reply to David Edmundson from comment #3) > What's the user-facing impact of this? As I said, some users use third party programs to get their tablets working. When they do so, it's up to this program to map the handedness, orientation and input/output area of the tablet. Right now, this cannot properly function because `kcm_tablet` also provides handedness and orientation settings; but the most important user-facing impact of this is being unable to map the output to a certain display area, such as a window, a window region, or a region between two displays (if for some reason there's someone with this kinda use case). `kcm_tablet` doesn't support any of those use cases, and third party software like OpenTabletDriver usually factor in all the monitors' position, orientation and size to calculate display areas, X11-style, and therefore the input will be spit out in absolute coordinates relative to the total graphical real estate available to the user. When KWin maps this "absolute input" to be relative to just a display, things break and the user (me) gets really confused. -- You are receiving this mail because: You are watching all bug changes.
