Bug 392400 - Painting cursor gets stuck outside the canvas area with the cursor of resizing the interface
Summary: Painting cursor gets stuck outside the canvas area with the cursor of resizin...
Status: RESOLVED DUPLICATE of bug 390642
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 4.0
Platform: macOS (DMG) macOS
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-27 10:04 UTC by silva
Modified: 2018-03-28 12:07 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Wacom Tablet Issue (698.83 KB, video/quicktime)
2018-03-27 10:04 UTC, silva
Details

Note You need to log in before you can comment on or make changes to this bug.
Description silva 2018-03-27 10:04:32 UTC
Created attachment 111679 [details]
Wacom Tablet Issue

If I move the painting cursor outside the canvas, it changes to the resizing dockers icon. If I move inside the canvas again, the resizing dockers icon doesn't change to the painting cursor and I cannot draw/paint anymore.

The only thing I can do to make the painting cursor come back is if I lift the pen from the tablet until it is not recognised by the tablet.
Needless to say that doing it constantly ruins the whole workflow and a pain to use Krita.

I believe it only started to happen in version 4. I have tried older Krita versions in the past and never had this issue.

I have also already reset the Wacom drivers, installed older driver versions, reinstalled Krita, reinstalled the system and tried in OSX Sierra and High Sierra. The issue is always present.

I even thought of eventually buying another tablet but I read the issue is also present in Intuos (I have a Bamboo).

Krita is the only software I have that has that strange issue. I attached a video for better understanding the issue.

Thanks a lot! Keep up the excellent work.
Comment 1 Halla Rempt 2018-03-28 12:07:10 UTC

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