Bug 344415

Summary: [WACOM INTUOS2] cursor issues: double cursor, no focus, using wacom mouse then tablet
Product: [Applications] krita Reporter: brusheco <ngmstudio>
Component: Tablets (tablet issues are only very rarely bugs in Krita!)Assignee: Krita Bugs <krita-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: halla
Priority: NOR    
Version: 2.9 Beta   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description brusheco 2015-02-21 01:07:22 UTC 
I've had this before but its more prevalent in the recent beta 3 than ever. Its really hurting my sessions now.

1. Double cursor : as you get close to the edge of the canvas one paint cursor remains on canvas, and regular arrow  cursor appears outside of it.

2. Can't draw on canvas unless I click somewhere outside the canvas first, like for example, a floating docker.

3.switching to tablet mouse confuses krita and same problems occur, switching back to pen stylus and everything works fine.

I have a wacom intuos 2, fairly old model, buts its worked fine up until this point so I don't think its an issue with hardware (it works fine everywhere else)

Happens after i've spent at least 15-20mins in krita. To be honest i've had quite a few graphics related issues since the implementation of multidocs.

my graphics card is :  Gtx 560 TI 2GB

Reproducible: Always
Comment 1 Halla Rempt 2015-02-21 08:09:20 UTC 
Did you by any chance set your tablet driver to mouse mode?
Comment 2 brusheco 2015-02-21 09:36:25 UTC 
i didn't, but the tablet auto switches modes when you change tools anyway
Comment 3 brusheco 2015-02-21 14:19:00 UTC 
to be clear, by change tools, i mean from mouse to stylus, not a tool in krita. The tablet driver recognizes when you switch, so you don't have set modes anyway.
Comment 4 Halla Rempt 2016-06-17 09:22:14 UTC 
I'm pretty sure most of these issues were fixed during the 2.9 series. I cannot reproduce any of them anymore. If you still have these problems with 3.0, please reopen the bug.