GNOME Bugzilla – Bug 787932
Xsetwacom End Of Life: Support Cintiq 27QHD Touch additional buttons
Last modified: 2021-06-09 16:02:12 UTC
Created attachment 360106 [details] Wacom Cintiq 27QHD product photo Hi Carlos and Gnome maintainers, Trying to solve issues with the ExpressKey Remote with Aaron and Ping: https://sourceforge.net/p/linuxwacom/bugs/345/#6c00, we realized that Xsetwacom is probably affected by Gnome environment new ways of handling tablets, and that's maybe the cause of the EKR stopping time to time. I use an Xsetwacom script waiting for the full support of the EKR: see bugs 786338 (https://bugzilla.gnome.org/show_bug.cgi?id=786338), 786326 (https://bugzilla.gnome.org/show_bug.cgi?id=786326) and 786324 (https://bugzilla.gnome.org/show_bug.cgi?id=786324) And I also use it to disable touch support because Krita is not yet ready to handle them correctly (I accidentally draw spots with my fingers instead of being able to navigate with gestures)... Additionally, Xsetwacom is going to his End Of Life according to Ping, and that's coherent with the transition to Wayland. So, it's a goal to support the additional buttons of the Cintiq 27 (tactile ones on top right, see pictures attached) to allow to disable touch support, launch Caribou or the Gome Control center, or other settings. Maybe it can be configured the same way than other ExpressKeys, with the switch between buttons you already created for the EKR. Thanks a lot !
Created attachment 360107 [details] Wacom Cintiq 27QHD additonal buttons
(In reply to Camille Bissuel from comment #0) > Created attachment 360106 [details] > Wacom Cintiq 27QHD product photo > > Hi Carlos and Gnome maintainers, > > Trying to solve issues with the ExpressKey Remote with Aaron and Ping: > https://sourceforge.net/p/linuxwacom/bugs/345/#6c00, we realized that > Xsetwacom is probably affected by Gnome environment new ways of handling > tablets, and that's maybe the cause of the EKR stopping time to time. > > I use an Xsetwacom script waiting for the full support of the EKR: > see bugs 786338 (https://bugzilla.gnome.org/show_bug.cgi?id=786338), 786326 > (https://bugzilla.gnome.org/show_bug.cgi?id=786326) and 786324 > (https://bugzilla.gnome.org/show_bug.cgi?id=786324) > > And I also use it to disable touch support because Krita is not yet ready to > handle them correctly (I accidentally draw spots with my fingers instead of > being able to navigate with gestures)... Hmm, yeah, that's unfortunate. > > Additionally, Xsetwacom is going to his End Of Life according to Ping, and > that's coherent with the transition to Wayland. True. Mutter could gain some envvar to avoid configuring tablets itself in order to allow xsetwacom-based scripts to work on x11, but that's a less and less futurable approach. > > So, it's a goal to support the additional buttons of the Cintiq 27 (tactile > ones on top right, see pictures attached) to allow to disable touch support, > launch Caribou or the Gome Control center, or other settings. Indeed, I heard about this kind of buttons already, but have little first hand experience with how they are seen. Could you provide evemu-record recordings for both the pad device (pressing those buttons) and the pen device (I need nothing in particular for this one, just need both recordings to replay/emulate the tablet entirely here). > Maybe it can be configured the same way than other ExpressKeys, with the > switch between buttons you already created for the EKR. Buttons with an etching should probably have hardcoded actions, rather than mappable. But the way I figured how it should work requires some support from libwacom to tell the action that corresponds to each button. Ping/Aaron, I see you're on CC, any input is welcome :).
Recent tablets like the Cintiq Pro 13 and Cintiq Pro 16 have similar hard coded actions keys which are supported in the kernel. I'm under the impression that Ping put in the work to support those in the kernel in part because we knew that xsetwacom would not be able to perform those actions in the future. For this action (disabling touch) even if we fixed it for the etched keys in the kernel (Cintiq 24 and Cintiq 27) there are other tablets (at least Intuos 5 and Intuos Pro) where the only way to disable touch is with xsetwacom. Most Wacom users disable touch, at least at some point. They need either a way to disable touch from the command line or to have that option in GNOME.
Created attachment 360168 [details] evemu-record for the Cintiq 27 buttons and pen Here is the log Carlos ;) As far as I can say as a user, it's fine if they are hardcoded for me, but maybe other users will want it to be mappable... I don't know how it supposed to work from the Wacom brand perspective on the Windows and Mac side But hardcoded is much better than nothing, so first thing first, and you don't have a lot of resources to waste ;p
I forgot to say that I touched buttons from left to right in the log... Maybe useful for mapping ;p
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help.