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 127680 - all gimp widgets should recognize XInput devices.
all gimp widgets should recognize XInput devices.
Status: RESOLVED DUPLICATE of bug 115774
Product: GIMP
Classification: Other
Component: User Interface
git master
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
Daniel Egger
Depends on:
Blocks:
 
 
Reported: 2003-11-22 18:22 UTC by Daniel Rogers
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Daniel Rogers 2003-11-22 18:22:38 UTC
I have a tablet in which all devices are set with "Always Core" so that I
can control my normal pointer with my stylus.

All widgets in the gimp should handle extended input devices that send
"always core" correctly.  Currently, in things like the tool box, if I try
to use the stylus to enter the menus, then the gimp switches between "Core
Pointer" and "stylus" very very quickly, sometimes causeing quirky and
undeseriable behaviour.  Like jumping out of the menus, selecting things
below the menus, etc.

I believe it is the same problem that cause the gimp to go, spontainously,
from me dragging the continuous region selection threshold widget, to the
"detached dialog box" when dragging the slider widget.  This is very annoying!
Comment 1 Sven Neumann 2003-11-22 18:58:55 UTC
All GIMP widgets handle all devices that send Core events. This bug
report has a bogus summary. It actually talks about the problem
described in bug #115774.

*** This bug has been marked as a duplicate of 115774 ***
Comment 2 Daniel Rogers 2003-11-22 19:30:19 UTC
hmm, I think I was confusing.  What I meant was that all gimp
windows/widgets/etc should recognize XInput devices and acitvate a
context change, etc.

I think this would avoid the the problem describe in bug #115774