After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686730 - Wacom calibration tool is difficult to use on pen-and-touch screens
Wacom calibration tool is difficult to use on pen-and-touch screens
Status: RESOLVED DUPLICATE of bug 680114
Product: gnome-control-center
Classification: Core
Component: Wacom
3.4.x
Other All
: Normal normal
: ---
Assigned To: Olivier Fourdan
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-10-23 21:05 UTC by Jason Gerecke
Modified: 2012-10-24 16:41 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jason Gerecke 2012-10-23 21:05:44 UTC
It is difficult to properly calibrate devices whose screens are both pen and touch sensitive. One must be careful to keep their hand off the touchscreen in order to calibrate, lest an errant contact be interpreted as intentional click. This makes it extremely challenging to get an accurate calibration since there is nothing to keep the hand (and by extension, the pen) steady.

Ideally, the calibration tool should ignore clicks from devices other than the one being calibrated. Alternatively, it may suffice to ignore all clicks more than some maximum distance away from the target's center.
Comment 1 Bastien Nocera 2012-10-23 21:22:02 UTC
We can easily get the device that generated the event so ignoring the events from other devices is probably the easiest thing to do.
Comment 2 Olivier Fourdan 2012-10-24 06:41:31 UTC
What version of GNOME is that? The calibration should select the appropriate tool in GNOME 3.6 and filter out other devices.
Comment 4 Bastien Nocera 2012-10-24 08:25:59 UTC
From the version field, I'd say 3.4.

Let's reopen if it's still broken in 3.6.

*** This bug has been marked as a duplicate of bug 680114 ***
Comment 5 Jason Gerecke 2012-10-24 16:41:06 UTC
I missed that bug in my search; good to know its already been addressed.