[kwin] [Bug 411877] Touchscreen input locked to first screen

2022-10-16 Thread David Sutton
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #24 from David Sutton --- So the first thing I had to do was find out which event was related to the touch screen - in my case event4 was the one I needed: "qdbus org.kde.KWin /org/kde/KWin/InputDevice/e

[kwin] [Bug 411877] Touchscreen input locked to first screen

2022-10-11 Thread David Sutton
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #22 from David Sutton --- FWIW: I was reading through the notes on the merge request when I noticed a comment saying that the ability to set it was already in there, it just wasn't exposed via a UI. I was able to find the input devic

[kwin] [Bug 411877] Touchscreen input locked to first screen

2022-10-10 Thread David Sutton
https://bugs.kde.org/show_bug.cgi?id=411877 --- Comment #20 from David Sutton --- Looking at the possible merge request, it seems to make two assumptions - that you only have two possible screens and that the screen isn't reporting any physical dimensions - which is likely to fix one use

[kwin] [Bug 411877] Touchscreen input locked to first screen

2022-03-15 Thread David Sutton
https://bugs.kde.org/show_bug.cgi?id=411877 David Sutton changed: What|Removed |Added CC||kant...@gmail.com --- Comment #9 from David

[kwin] [Bug 428760] Map/Remap touch input ONLY to related touchscreen panel

2022-02-28 Thread David Sutton
https://bugs.kde.org/show_bug.cgi?id=428760 David Sutton changed: What|Removed |Added CC||kant...@gmail.com -- You are receiving this