https://bugs.kde.org/show_bug.cgi?id=411877
--- Comment #3 from lo...@kde.bt.alestan.publicvm.com --- So I finally had a bit more time to dig into this, with a bit of grepping, I managed to find the relevant function: $kwin/libinput/connection.cpp:applyScreenToDevice Looks like there is no simple way to remap APDs to arbitrary virtual screen offsets. That said, adding additional heuristics for the mapping is pretty simple (for one, if there is only a single display attached, grab it with reasonable confidence, also, if there is already a APD attached, grab the next screen in line). It also should be easy to add a config file to override the auto-detection. Given the information available in the function, looks like mapping from touch device to EDID is going to be the most reliable. I'm not certain how to identify the touch device, as USB serial numbers are unreliable, and bus location is worse. I'll poke that a bit more and see what shakes out. All that said, I'm happy to attach a patch once I get it working, if I can get some help making sure it won't just waste everyone's time. To that end, I have a few questions. 1. Is it better to add a new section to one of the existing $HOME/.config/k*rc files, or to make a new ktouchrc (or some other name) file? 2. Do I put the config reading/writing inline in the `applyScreenToDevice` function, or in its own function (and where do I put that)? 3. Is there a better choice than EDID to remember the display, and is there an obvious choice for the input device? -- You are receiving this mail because: You are watching all bug changes.
