Bug 406863 - Wacom Cintiq Pro32 stops tracking stylus when lifted and returned to canvas space
Summary: Wacom Cintiq Pro32 stops tracking stylus when lifted and returned to canvas s...
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 4.1.7
Platform: Microsoft Windows Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-24 23:35 UTC by Brian
Modified: 2019-05-05 11:25 UTC (History)
2 users (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 Brian 2019-04-24 23:35:54 UTC
SUMMARY


STEPS TO REPRODUCE
1. Launch Krita on a Wacom Cintiq Pro32 display
2. Draw on the canvas space with any brush
3. Lift stylus 1/4" or more
4. Without bringing it down outside of the canvas space, bring it back down within the canvas space and attempt to draw more

OBSERVED RESULT
The brush cursor remains wherever it was before and does not track the stylus movement.  Moving the stylus to anywhere else on the screen that uses the system pointer cursor (instead of the brush cursor) "resets" this behavior and you can move it back into the canvas and draw more (until you lift it from the display and try to bring it back down).  Effectively, this requires you to use the stylus and never pick it up more than 1/4", even if having to move your arm to the other end of the canvas, etc.  This behavior did not exist with Wacom Intuous Pro or Wacom Cintiq 24HD on the same system.

EXPECTED RESULT
Lifting the stylus and returning it to the screen should result in the tracking being resumed and allow you to continue to draw.

SOFTWARE/OS VERSIONS
Windows: Windows 10, v1903
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Alvin Wong 2019-04-26 15:34:55 UTC
Hi Brian, thanks for your report. I see that your bug report is filed against 4.1.7, but we've recently made some significant improvements on the tablet support so your report might no longer apply. These improvements will come with the upcoming version 4.2.0 which is set to be released around the end of May.

In the meantime, the nightly builds already contain these improvements so I would like to ask you to test it out and see whether this issue can still be reproduced. You can find the nightly builds here: https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/
Please keep in mind that the nightly builds are not of release quality and may contain bugs so they should not be used for any serious work, but only for testing.

Please kindly test with the nightly build and let us know whether this issue is still reproducible. If it is reproducible, I would like you to obtain a tablet log to help with debugging the issue. You can obtain a tablet log by following these instructions: https://docs.krita.org/en/KritaFAQ.html#windows
Comment 2 Brian 2019-05-05 01:45:51 UTC
Yay!  The nightly build works just as expected (and the way 4.1.7 works with my other Wacom devices).  Looking forward towards being able to use it.  Is there a rough ETA for when 4.2 stable may be coming?

Thanks!
Comment 3 Bug Janitor Service 2019-05-05 04:33:12 UTC
Thanks for your comment!

Automatically switching the status of this bug to REPORTED so that the KDE team
knows that the bug is ready to get confirmed.

In the future you may also do this yourself when providing needed information.
Comment 4 Halla Rempt 2019-05-05 11:25:43 UTC
End of this month :-)