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 639902 - Cursor misaligned Wacom Graphire 2
Cursor misaligned Wacom Graphire 2
Status: RESOLVED DUPLICATE of bug 154657
Product: GIMP
Classification: Other
Component: User Interface
2.6.11
Other Windows
: Normal major
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2011-01-18 22:09 UTC by Roberto Muscia
Modified: 2011-06-16 09:24 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Roberto Muscia 2011-01-18 22:09:29 UTC
When using drawing tools or selection tools the displayed cursor still (as long as I know Gimp) might not correspond with the drawing location.

The misalignment can be minor or huge. It totally depends on lifting up the mouse (like disconnected) and placing it back somewhere else on the tablet.
That behavior can be used for correcting the misalignment by a trial and error process of lifting up the mouse and placing it back on the tablet but it's a time consuming alternative.

Cursor above menus is properly aligned.

Pen isn't recognized at all.

Standard mouse with a direct connection to the pc(no tablet) works fine.

I think tablet support these days is not something to postpone fixing so I gave this topic a "major" but others might very well think differently about it.
On the other hand: I have no idea how other tablets perform in Gimp, though.
Comment 1 Michael Schumacher 2011-01-18 22:38:56 UTC
Duplicate of bug #154657?
Comment 2 Roberto Muscia 2011-01-19 17:06:26 UTC
bug #154657 is 6 years old. Issue still stands in Gimp 2.6.11. So if identical bug reports then consider it as a reminder :-P
Comment 3 Michael Schumacher 2011-06-16 09:24:28 UTC
Thanks for the bug report. 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 154657 ***