Bug 106073 - GIMP cannot handle extended input devices correctly
Summary: GIMP cannot handle extended input devices correctly
Status: RESOLVED INVALID
: 86598 (view as bug list)
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: X11 Applications (show other bugs)
Version: Beta 1
Hardware: i686 SUSE Other
: P5 - None : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: Stefan Dirsch
URL: http://bugzilla.gnome.org/show_bug.cg...
Whiteboard:
Keywords: should_go_upstream
Depends on:
Blocks:
 
Reported: 2005-08-22 06:54 UTC by Ulrich Windl
Modified: 2006-10-31 16:08 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ulrich Windl 2005-08-22 06:54:53 UTC 
When configuring GIMP for extended input devices (Core Pointer: Mouse, Wacom
Stylus, Wacom Eraser, Wacom Mouse), GIMP does not detect a change of the
extended input device. Instead the currently selected tool (e.g. Stylus) remains
active. That tool however cannot activate any icons in GIMP's toolbox, just as
clicking with the mouse (Core Pointer) to any GIMP dialog elements produces no
action at all.
See also http://bugzilla.gnome.org/show_bug.cgi?id=306616 (reported before)
Comment 1 Ulrich Windl 2006-01-11 09:21:42 UTC 
The bug ist stil lthere, but I found out that
1) GIMP "grabs" the input device (no other windows will receive mouse clicks as well)
2) Pressing F10 (activate menu) followed by ESC (cancel menu) reactivates the plain old mouse keys (mouse moves are active all the time)
Comment 2 JP Rosevear 2006-04-13 23:58:20 UTC 
*** Bug 86598 has been marked as a duplicate of this bug. ***
Comment 3 JP Rosevear 2006-10-31 16:08:02 UTC 
Recently the upstream bug was marked obsolete.  I'll assume its the case in 10.2 now.