[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #12 from jan.clausse...@web.de --- I have found a workaround for me some time ago. Since I wrote a script that opens Xournal++ when I press the top button of my Bamboo Ink, I also made it map the Wacom tablet onto my laptop's monitor, which is called eDP1 in my case. I am aware that this might not be the case for all laptops. Maybe xrandr should provide a possibility to detect differentiate it from the external monitor. Here are my commands from the script xsetwacom --set "Wacom Pen and multitouch sensor Pen stylus" MapToOutput "eDP1" xsetwacom --set "Wacom Pen and multitouch sensor Pen eraser" MapToOutput "eDP1" xsetwacom --set "Wacom Pen and multitouch sensor Finger touch" MapToOutput "eDP1" -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 maxmustermann1...@web.de changed: What|Removed |Added CC||maxmustermann1...@web.de -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #11 from daniel-other+kde...@dadosch.de --- Hi Valerii, I've just built the current master and tested it. It doesn't seem to be fixed (the second issue in your list, at least). This shows up in the log (But this might be intentional to some degree, when I see the comment in the code for this.): > Couldn't load plugin "kcms/kcm_wacomtablet" : "The shared library was not found." -- falling back to old-style loading from desktop file org.kde.wacomtablet.kcm: Call to TabletAreaSelectionView::setupScreens made with no valid screens. org.kde.wacomtablet.kcm: Internal error, invalid tablet geometry - "0 0 0 0" org.kde.wacomtablet.kcm: Call to TabletAreaSelectionView::setupScreens made with no valid screens. org.kde.wacomtablet.kcm: Internal error, invalid tablet geometry - "0 0 0 0" If I connect my laptop to an external screen, set the touch screen area to only the laptop screen, then save it. Now if I disconnect & reconnect the external screen, the touch screen area are the full virtual screen, not only the laptop screen as previously set. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #10 from Valerii Malov --- Daniel, indeed I'm not sure if there's a way to determine which screen the built-in tablet belongs to, although I haven't checked on libwacom API in a while. I'll try to look into that PR again later. I've looked into the issue of losing settings, seems like a two-fold problem: 1. Single-screen setups are always mapped to desktop, not specific screen. IIRC this was done to support relative mapping mode since it only works when the tablet is mapped to the whole desktop. 2. When a screen goes missing, mapping defaults to desktop and this setting is saved, which breaks the mapping when the screen is reconnected. For now as a workaround I've disabled saving the "default" desktop to tablet profile. This should in theory address 2nd and somewhat 1st issue. If anyone can build & test current master that would be swell. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #9 from Valerii Malov --- Git commit 1d0b04478c9eb7df24a664ba7cc5096c5b0ee675 by Valerii Malov. Committed on 02/07/2020 at 21:14. Pushed by valeriymalov into branch 'master'. don't override the screenspace in profile if the screen is missing M +12 -12 src/kded/tablethandler.cpp https://invent.kde.org/system/wacomtablet/commit/1d0b04478c9eb7df24a664ba7cc5096c5b0ee675 -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #8 from jan.clausse...@web.de --- Will try tomorrow. Thank you! -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #7 from daniel-other+kde...@dadosch.de --- Ok, so I have started to work on this a bit: https://invent.kde.org/system/wacomtablet/-/merge_requests/1 I've implemented a boolean which reads from libwacom wether it is a built in device (tablet on screen or tablet on system). HOWEVER, the main thing, to determine the correct screen must still be done. I know nothing about the gui stuff, but I would do it the following way: If it is a built-in-device, disable the normal screenspace selector, and enable a special selector of the screen. This screen selection should be saved like normal in the config. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #6 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/system/wacomtablet/-/merge_requests/1 -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #5 from Michael Zapf --- For now, I wrote a script ~/bin/wacom that runs xsetwacom and xrandr to configure the tablet. I added two shortcuts to the plasma desktop for turning tablet support on and off. This is, of course, just a workaround. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #4 from jan.clausse...@web.de --- Well, but it doesn’t work. As soon as I connect a screen the whole area of both screens is mapped. I habe to set it again every time. Maybe there should be a checkbox for that in KDE‘s settings then for cases where it doesn’t recognize the screen. I have an X380 Yoga and usually ThinkPads have great Linux support. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 --- Comment #3 from daniel-other+kde...@dadosch.de --- Actually, libwacom provides a flag, wether the tablet is built-in within a screen. (See https://github.com/linuxwacom/libwacom/blob/2dd3501fd3dd422127299a61692a798226ddfb11/libwacom/libwacom.c#L259) This means that kde's wacomtablet should be able to identify such tablet and map the correct screen to it automatically. Further, all options which do not make sense for a screen-tablet should be disabled (relative tracking etc) -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 Michael Zapf changed: What|Removed |Added CC||b...@mizapf.de --- Comment #2 from Michael Zapf --- My issue seems to be the same: I am using a Cintiq tablet on HDMI-1 output, and I have to select the tablet area as the HDMI-1 area only so that the touch position and the pointer match. However, every time I turn off the tablet and back on, the setting is reset to the complete screen (HDMI-0 + HDMI-1). This means I always have to redo the setting. -- You are receiving this mail because: You are watching all bug changes.
[wacomtablet] [Bug 419392] Settings for touch zone are not saved
https://bugs.kde.org/show_bug.cgi?id=419392 daniel-other+kde...@dadosch.de changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||daniel-other+kdebug@dadosch ||.de --- Comment #1 from daniel-other+kde...@dadosch.de --- I also have this problem. It is very annoying. One could workaround this by executing the corresponding xsetwacom set … command, but this is not very practicabel. One way to solve this would be to add a checkbox "always use the touchscreen/peninput as input for screen $SCREEN", which would be a viable solution, especially for 2-in-1 devices. Also for regular wacom-pads this would be a good solution, because their users simply don't activate that checkbox and thus they get their wanted behaviour. -- You are receiving this mail because: You are watching all bug changes.
