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 349864 - Top button of Wacom Volito 2's pen only produce right click
Top button of Wacom Volito 2's pen only produce right click
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Win32
2.10.x
Other Windows
: Normal normal
: ---
Assigned To: gtk-win32 maintainers
gtk-bugs
: 554808 653694 762343 (view as bug list)
Depends on:
Blocks: 784342
 
 
Reported: 2006-08-03 23:30 UTC by Joakim
Modified: 2018-05-02 14:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joakim 2006-08-03 23:30:25 UTC
Please describe the problem:
I'm using a Wacom Volito 2 tablet (driver v. 4.95-6) with Gnome 2.2.12 under WindowsXP and GTK+ 2 (v. 2.8.18.)

The top button can't be assigned to do anything, all it does is right clicking. The button doesn't appear in the Device dialog.

Steps to reproduce:
1. Open the configuration panel for Wacom from the control panel.
2. Set the top button to erase (or anything else for that matter)
3. Start Gimp and create a new document
4. Press the topbutton somewhere on the canvas


Actual results:
Instead of erasing, the right click menu appears instead

Expected results:
Erase

Does this happen every time?
Yes

Other information:
As said before, there is no graphical representation of the button in the Device dialog.
Comment 1 Sven Neumann 2006-08-07 14:38:31 UTC
This seems to be a problem in the tablet support in GTK+ then. Please check the
GTK+ product for duplicates before you reassign this bug-report to it.
Comment 2 Sven Neumann 2006-08-15 10:48:55 UTC
Joakim, any particular reason why you haven't reassigned the bug report yet?
Comment 3 Tor Lillqvist 2007-01-22 12:49:03 UTC
Setting the pen top button function in the Control Panel's Wacom applet isn't going to make any difference for GIMP or GTK+ apps in general. I have no idea how that preference would be visible programmatically.

The intention is that one sets up the function of tablet pen buttons in GIMP, I assume. But there seems to be some problem with the Configure Extended Input Devices dialog on Win32. Hard to say whether they are caused by problems in the WinTab code in gdk/win32, or problems in GIMP's code. When opening the Configure Extended Input Devices dialog, for some reason the "WACOM Tablet Puck" device is selected (although I don't have any puck). And there are two copies of each device: WACOM Tablet Puck, WACOM Tabler Pressure Stylus, WACOM Tablet Eraser Stylus. If I select one of the "WACOM Tablet Pressure Stylus", I get output like this:

(gimp-2.2.exe:2960): Gtk-CRITICAL **: gtk_scrolled_window_add: assertion `bin->child == NULL' failed
(gimp-2.2.exe:2960): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed
(gimp-2.2.exe:2960): Gdk-CRITICAL **: gdk_window_set_background: assertion `GDK_IS_WINDOW (window)' failed
(gimp-2.2.exe:2960): Gtk-CRITICAL **: gtk_scrolled_window_add: assertion `bin->child == NULL' failed
(gimp-2.2.exe:2960): Gtk-CRITICAL **: gtk_widget_realize: assertion `GTK_WIDGET_ANCHORED (widget) || GTK_IS_INVISIBLE (widget)' failed
(gimp-2.2.exe:2960): Gdk-CRITICAL **: gdk_window_set_background: assertion `GDK_IS_WINDOW (window)' failed
Comment 4 Tor Lillqvist 2007-01-30 23:32:30 UTC
The warnings mentioned above are caused by bug #399425 (which includes a fix).
Comment 5 Michael Schumacher 2009-09-14 07:59:58 UTC
*** Bug 554808 has been marked as a duplicate of this bug. ***
Comment 6 Michael Schumacher 2011-07-03 07:30:11 UTC
*** Bug 653694 has been marked as a duplicate of this bug. ***
Comment 7 Michael Schumacher 2017-02-21 09:29:00 UTC
*** Bug 762343 has been marked as a duplicate of this bug. ***
Comment 8 GNOME Infrastructure Team 2018-05-02 14:20:15 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gtk/issues/264.