Bug 341396 - Mapped Wacom Intuos4 for Mouse Mode, Krita doesn't register
Summary: Mapped Wacom Intuos4 for Mouse Mode, Krita doesn't register
Status: RESOLVED DUPLICATE of bug 342055
Alias: None
Product: krita
Classification: Applications
Component: Usability (show other bugs)
Version: unspecified
Platform: Microsoft Windows Other
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-29 10:12 UTC by spottedsky
Modified: 2014-12-23 09:24 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description spottedsky 2014-11-29 10:12:11 UTC
I have mapped my Wacom Intuos4 to be in Mouse Mode, but Krita does not register this setting. Whenever I am in Mouse Mode and press down with the stylus, the cursor will jump to the right and onto a different part of the program. When I lift my stylus, the cursor returns to the position where I pressed down. I have added Krita to my Applications in Tablet Properties and set the program to register Mouse Mode. It produced no results. I tested Pen Mode for Wacom Intuos4 in Krita to see if I could produce the same results. Pen Mode works as it usually would. Mouse Mode continues to not work.

Reproducible: Always

Steps to Reproduce:
1. Open Krita after adding it in the Applications of the Wacom Tablet Properties and setting it to Mouse Mode
2. Open a new canvas
3. Using a Wacom Intuos4 in Mouse Mode, press down with the stylus onto the tablet

Actual Results:  
Cursor jumps across the screen and presses onto a different position. After lifting stylus off the tablet, cursor returns to the original point.

Expected Results:  
Cursor should have remained in the position where which the stylus was pressed down upon.
Comment 1 Halla Rempt 2014-12-09 15:25:47 UTC
Hm... I actually am afraid that this is sort of by design... We implemented our own wintab support and only implemented the 'normal' mode :-(
Comment 2 Halla Rempt 2014-12-23 09:24:26 UTC

*** This bug has been marked as a duplicate of bug 342055 ***