Bug 260482

Summary:	when using a stylus, 2nd and 3rd buttons act as 1st button
Product:	[Applications] calligracommon	Reporter:	enkithan
Component:	general	Assignee:	Calligra Bugs <calligra-bugs-null>
Status:	CONFIRMED ---
Severity:	normal	CC:	arvid2000, jonas.vejlin, lambdae2, mmtsales
Priority:	NOR
Version First Reported In:	2.0
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description David Faure 2010-12-17 19:41:15 UTC



---- Reported by enkithan@free.fr 2008-06-23 21:22:55 ----

Version:           trunk (using Devel)
Installed from:    Compiled sources
Compiler:          gcc 4.3.1 
OS:                Linux

using:
archlinux i686
qt-copy 819958
kdelibs4 trunk 822761
koffice2 svn 823507
wacom intuos 3

When I use the stylus of my tablet on the canvas/page/viewport, 2nd and 3rd buttons act as 1st button 

Exemple: Instead of showing the right clic menu, the current tool is used; but if I right-click on any elements of the UI, right click works.

What is interesting is that the intuos3 mouse works as expected.



---- Additional Comments From jonas.vejlin@gmail.com 2009-04-05 09:12:35 ----

can you confirm that this problem still exist in koffice2?



---- Additional Comments From enkithan@free.fr 2009-04-05 12:00:37 ----

yeah the bug still happens here, using qt4.5, kde 4.2.2 and koffice trunk.

I think it's a koffice-only bug, since 2nd & 3rd buttons works fine in all others Qt/KDE apps I tried.



---- Additional Comments From zander@kde.org 2009-04-05 12:12:32 ----

You might want to check if you have libwacomcfg.so* installed. (package wacom-tools on debian) That helps Qt detecting exactly which pen/stylus etc you are using.



---- Additional Comments From enkithan@free.fr 2009-04-05 13:33:04 ----

Yes, I have the file, it's installed with linuxwacom drivers on my distrib.

Just found something interesting: the bug also happens with Koffice beta3 on WindowsXP.



---- Additional Comments From lambdae2@gmail.com 2009-04-05 21:52:36 ----

2nd & 3rd buttons of the stylus simply don't do anything for me in the canvas, they do work in other parts of the gui, so I can sort of confirm, I have Bamboo Fun tablet, tablet mouse works.



---- Additional Comments From zander@kde.org 2009-10-12 11:04:37 ----

Is this still a problem?



---- Additional Comments From enkithan@free.fr 2009-10-12 11:56:36 ----

Yes :/
to be more precise, stylus buttons behave like the tip at minimum pressure.



--- Bug imported by faure@kde.org 2010-12-17 19:42  ---

This bug was previously known as bug 164782.

Comment 1 Halla Rempt 2012-04-16 13:36:29 UTC

This is no longer a problem in Krita. In Words, the right-click menu doesn't appear when using the stylus button. But I doubt that's actually a problem. Karbon uses middle-mouse button for drawing straight lines, and Karbon doesn't see the stylus buttons either.

This is not a wacom problem, but a problem in handling the tablet events in flake and those apps. The code in KoToolProxy::tabletEvent sufficiently shows how complex this can get...

Comment 2 Marcelo Sales 2016-05-02 00:04:46 UTC

I'm experiencing this problem right now using Kubuntu packages. I'm running Kubuntu 14.04.04, with the KDE Backports PPA. KDE version is 4.14.13. My tablet is a Intuos Pro Small (PTH-451).
The strange thing is that I run the same KDE version on another computer, a notebook, and everything works fine there, with the very same tablet. Also, I was running Kubuntu 14.10 on the problematic computer before downgrading to 14.04.04 (fresh install), and the stylus buttons were working fine then too.
If I uninstall the xserver-xorg-input-wacom package, the tablet is not detect as a tablet (as expected), but I still can use it as a mouse and the stylus buttons work fine (as middle and right buttons). However, with this package installed, the tablet is detected correctly and all of its functions are available, including the Input Devices settings in KDE System Settings, except for the stylus buttons, which always work as left clicks, no matter what I set them up to do in System Settings.
It looks like a configuration problem, rather than a bug, but I have no idea how to fix this...