GNOME Bugzilla – Bug 737758
Digitizer calibrations should be cached for each display configuration
Last modified: 2016-03-10 14:56:16 UTC
I have a Thinkpad Yoga laptop with a builtin wacom digitizer. When I change my display configuration, (such as by doing an xrandr rotate, or by plugging in an external monitor), I get a notification saying: Calibration needed Tablet Wacom ISDv4 EC needs to be calibrated And it gives me a handy button to press to launch a nifty little calibration program. It's really nice to have this calibration so well integrated. I think this is a fairly recent addition, and I really appreciate it. Thanks! But, the problem is that it prompts me to re-calibrate at every change, (even when I change to a configuration I've used before and have already calibrated). This turns the convenient feature into a nuisance, (aggravated by the fact that the disappearance of the notification bar at the first click within the calibration causes the targets to move and forces a second pass through the calibration). What would be exceedingly convenient is if the calibration settings were cached specific to a particular display configuration and re-used. -Carl
Thanks for the bug report! I even think we could be able to reuse the same calibration data for rotated screens, at least if the device has the same units/m on both axes (which I don't think there's many exceptions to that). I'd say recalibration in these situations is actually mainly useful if the ratio actually changes (eg. setting 1024x768 on a wide screen), this is not as frequent by far. Some caching might still be positive though.
Hi Carlos... there's bug #741738, bug #735981 and bug #732600 which all seem to be pretty much the same root issue as this. Is it? It's a bit confusing with so many bug reports around "wacom + calibration".
Thanks for taking the time to report this. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 748659 ***