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 612767 - Tablet only recognized as pen mode in GIMP, as opposed to mouse mode
Tablet only recognized as pen mode in GIMP, as opposed to mouse mode
Status: RESOLVED DUPLICATE of bug 154657
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.16.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2010-03-13 03:40 UTC by Tara
Modified: 2010-05-20 19:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Tara 2010-03-13 03:40:30 UTC
When using my tablet to attempt drawing on GIMP, instead of recognizing it as Mouse Mode as the rest of the computer does GIMP will only recognize it as pen mode which makes drawing difficult.

In Pen Mode it treats the space of the tablet as though it's the whole screen--however in Mouse Mode it treats it as though I was using a mouse which is my preferred mode.  Is there something I'm doing wrong?  I've installed and reinstalled both and updated both(the tablet drivers and GIMP) and it's staying the same.  Is there any way to fix this or will I just have to deal with it until the next update?

I also tried using an older version--it didn't work.
Comment 1 Michael Schumacher 2010-03-13 11:32:40 UTC
Duplicate of bug #154657?
Comment 2 a783092 2010-03-14 00:37:37 UTC
I'm having this exact same problem. I'm running Vista and using a Wacom Intuos 3.

(In reply to comment #1)
> Duplicate of bug #154657?

It is not. Basically, the problem is that GIMP is recognizing the tablet as if I were drawing directly on the monitor itself. So when I touch the stylus to one part of the tablet, I can draw and such as I would with a mouse, however, when I lift up and move the stylus to another section, the cursor jumps over accordingly as opposed to staying where it is, as a mouse would. You know how, if you move your mouse to the edge of your mouse pad, you can pick the mouse up, move it back to the center and the cursor stays where it is? Pen mode doesn't let you do that. It moves the cursor in correspondence with where you touched the stylus back down.

You can change the settings for the tablet itself so that it can either operate as mentioned above or as a mouse would. However, GIMP doesn't care what your settings are and treats it like a pen anyway. 

I have one other symptom: for some reason when I use the pen tool, the cursor for the pen itself (the little dot that represents the size and placement of the actual pixels I'll be placing on the canvas) and the mouse pointer (the actual arrow clicker thingy you use in, you know, every other program ever) start will to de-synchronize after a few seconds. The pen cursor moves slower, for some reason, so I end up moving the mouse cursor across the screen while the pen cursor only moves about half the distance. On top of that, because GIMP is recognizing the tablet as being in "pen mode", the cursors maintain a constant distance when I lift up the stylus and move it. So the only way to get the cursors to synch back up is to move the mouse cursor in the general direction of the pen cursor. This only happens when I use my tablet. No problems at all with the mouse.

It's worth it to note that I recently installed the drivers for my tablet. I'd used the same version of GIMP prior to that and had none of these problems, but GIMP also did not recognize pressure sensitivity (likely because it thought I was using a mouse).
Comment 3 Sven Neumann 2010-03-14 09:24:59 UTC
It is definitely not GIMP's job to deal with this. Handling of different tablet modes takes place in the tablet driver and GTK+. So this bug-report doesn't belong here. To me it looks a lot like a duplicate of bug #154657 though.
Comment 4 Javier Jardón (IRC: jjardon) 2010-05-20 19:33:07 UTC

*** This bug has been marked as a duplicate of bug 154657 ***