[kwin] [Bug 411877] Touchscreen input locked to first screen
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/event4 org.freedesktop.DBus.Properties.Get org.kde.KWin.InputDevice touch" returns "true" I went ahead and used kinfocenter ( Graphics -> Wayland ) to confirm which monitor I needed to assign it to - it gives the mapping from the monitor name to the device name. I then set event4 to the right monitor ( outputName ) : "qdbus org.kde.KWin /org/kde/KWin/InputDevice/event4 org.freedesktop.DBus.Properties.Set org.kde.KWin.InputDevice outputName DP-2" -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
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 device via DBUS and changed the outputDevice to my touchscreen ( I have DVI-D-1, DP-1, DP-2, with touchscreen being DP-2 but it selects DVI-D-1 as is the primary screen and touchscreen dimensions don't match ) and now I can now control the touchscreen by touching it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
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 case but not one whether there is more than 2 screens or where the device is reporting dimensions that are different to the dimensions being reported by the touchscreen - examples of one or the other being listed in the comments on this bug, -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 411877] Touchscreen input locked to first screen
https://bugs.kde.org/show_bug.cgi?id=411877 David Sutton changed: What|Removed |Added CC||kant...@gmail.com --- Comment #9 from David Sutton --- Just for clarification, with X11 you can use xinput to force which display the touchscreen is bound to, unfortunately with wayland then it sounds like this is the responsibility of the compositor to track/maintain it -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428760] Map/Remap touch input ONLY to related touchscreen panel
https://bugs.kde.org/show_bug.cgi?id=428760 David Sutton changed: What|Removed |Added CC||kant...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
