Bug 359723 - [WACOM BAMBOO] Wrong mapping of tablet /stylus buttons
Summary: [WACOM BAMBOO] Wrong mapping of tablet /stylus buttons
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 3.0 Alpha
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-23 21:16 UTC by Bruno de Souza Lino
Modified: 2016-06-16 12:32 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Log of the issue. (1.10 MB, text/plain)
2016-02-23 21:17 UTC, Bruno de Souza Lino
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Bruno de Souza Lino 2016-02-23 21:16:27 UTC
The current and previous alpha version of Krita seem to have wrong mappings for where the tablet buttons are. My stylus buttons are mapped in reverse ( the button close to the tip does the mapping of the button away from the tip and vice versa) and only 3 of the 4 tablet buttons work,

Reproducible: Always

Steps to Reproduce:
1. Open Krita 
2. Create a new document
3. Press your tablet and stylus keys

Actual Results:  
The buttons are mapped wrong and either don't work or do the mapping of other buttons.

Expected Results:  
The buttons should do the thing they were mapped to do.

Wacom Bamboo MTE 450 Tablet
Windows 10 Home x64
Comment 1 Bruno de Souza Lino 2016-02-23 21:17:33 UTC
Created attachment 97382 [details]
Log of the issue.

Log displaying the bug in action.
Comment 2 Dmitry Kazakov 2016-05-17 11:11:06 UTC
Hi, Bruno!

I'm afraid I cannot reproduce you issue. If I remap my buttons in the Wacom driver configuration, everything works fine, *but* I should restart Krita to take the settings into effect. Did you restart Krita after changing settings in the driver?

Sometimes, quite rarely though, the Wacom driver goes crazy and starts telling us weird things, then a system reboot is needed.
Comment 3 Bruno de Souza Lino 2016-05-19 05:23:40 UTC
I'm gonna give it a test as of writing this comment. The issue seems to have been fixed in one of the alphas, though I'll just confirm it.
Comment 4 Halla Rempt 2016-06-16 12:32:12 UTC
Okay, I will close the issue now.