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 136790 - randomly switching tools with wacom tablet
randomly switching tools with wacom tablet
Status: RESOLVED DUPLICATE of bug 115774
Product: GIMP
Classification: Other
Component: General
1.x
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2004-03-10 19:06 UTC by brett hartshorn
Modified: 2004-07-04 00:46 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description brett hartshorn 2004-03-10 19:06:05 UTC
Extended input devices are not saved once configured from
file>preferences>input_devices>configure_extended_input_devices
The configuration only lasts as long as the current gimp session.

So, after closing and reopening the gimp, the wacom tablet tools default
back to core pointer.  And, inorder to gain pressure sensitity, one needs
to reconfigure the devices again from:
file>preferences>input_devices>configure_extended_input_devices

Also when flipping the stylus around quickly, or when quickly removing it
from the screen, parts of the image will become erased.  It seems that the
eraser tool is some how momentarily choosen, and then erases part of the
screen.

Gimp1.2 has neither of these problems.

Using Gimp2.0pre4 on redhat9, with an Intuos2,

-brett
Comment 1 Sven Neumann 2004-03-10 19:18:37 UTC

*** This bug has been marked as a duplicate of 128588 ***
Comment 2 Simon Budig 2004-03-10 19:23:25 UTC
The first part of the bug report has been dealt with in CVS, see
bug #128588 (You need to save the tool options once to keep the
input devices active, there now is a more obvious button for that).

I have not yet heard of the second problem. Is any of your devices
configured to the eraser? Please look this up in the "Device Status"
dialog. If there is such a tool and you configure it to something else
- does this change the described behaviour?

(for the future: Please open multiple bug reports for different
problems, so that we can keep track of them more easy.)
Comment 3 Simon Budig 2004-03-10 19:24:43 UTC
Reopening because the second issue is not covered by the other bug. We
should focus on that issue for this bug number.
Comment 4 brett hartshorn 2004-03-10 21:33:08 UTC
I have done more testing trying to figure out the second part of the
problem.  It seems that when the stylus is pulled away from the tablet
very very quickly, every once in awhile gimp will default back to the
core pointer.  And if the core pointer is assigned to the eraser tool,
then a few erase marks will appear on your image.  Some times the
marks will appear on after the other over a time of about one second,
and then it will stop.  I do not know how the internal code of the
gimp works, but from what it appears to me is there are two things
happening.

1. Sometimes gimp will default to core pointer.
2. Sometimes, if moving the stylus quickly and removing it quickly, it
appears the stylus movements and pressure settings are stored in a
queue, and that queue will still be played back even if the stylus
leaves the tablet surface.

3. This causes the problem that the 'stylus event queue' still plays
back even after (1) gimp has switched to core pointer.

-brett
Comment 5 Sven Neumann 2004-03-15 01:55:27 UTC
It would be very helpful to get a meaningful subject for this report.
Comment 6 Simon Budig 2004-03-15 10:15:38 UTC
I did not yet come around to test this with my tablet, but from the
description it sounds a lot like a GTK+/XFree86 problem. Could you
please tell us, what GTK+-Version and what XFree86 Driver you are
using? Did you install the linuxwacom drivers? Is your Tabled an USB
or a serial model?
Comment 7 brett hartshorn 2004-03-15 22:31:43 UTC
I am using XFree86-4.3.0-2.90.55, gtk2-2.2.2-1, and gtk+-1.2.10-25,
with a wacom intuos2 USB, on redhat9.  Wacom beta drivers 0.6 and
wacom.c module v1.30-j0.5.2.

I do not think it is a bug in XFree86, or the wacom drivers, becuase
gimp 1.2 does not have this problem on the same machine.  Maybe
something has changed in gtk2 that is causing the problem?

-brett
Comment 8 Sven Neumann 2004-07-04 00:46:41 UTC

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