https://bugs.kde.org/show_bug.cgi?id=368351

--- Comment #4 from Julien Duminil <dumi...@free.fr> ---
Hello,

I bought a XP-Pen Star 03 and I am experiencing the same kind of problems.
My guess is that this bug is related to bugs 363284 and 367618.

To be more precise on what's happening to me:

The *outline shape* on the canvas stops to follow the *cursor shape* when I
lift up the pen slightly above the tablet, even after putting down the pen near
the tablet surface. Note that the *cursor shape* still follows the pen!
I have enabled *outline shape* and *cursor shape* in general settings to
actually see the desync, so those who have not enabled *cursor shape* see the
*outline shape* as freezed (as in bug 367618). The brush starts to sync again
with the cursor when the pen touch the tablet (making strokes as in bug
363284), or when the cursor goes out of the canvas, or when I press a pen
button, or when I move the mouse. Note that the *cursor* is *always* moving
well with the pen, inside Krita and outside of Krita.

>From what I'm understanding by reading the related bug reports, it may be
related to the wintab driver not handling very well the proximity
notifications. Are there reasons for the brush to not follow the cursor
position? (precision?) Maybe you can try to reproduce the bug by introducing in
the code some fake random TabletLeaveProximity (if it is the culprit)? Or maybe
we could have an option to process TabletMove whatever
TabletEnterProximity/TabletLeaveProximity said (if it's not already the case,
I've not seen the code actually, just the logs from another thread)? Or an
option to always use the mouse position instead of the tablet position?

I hope this brings you some useful informations. Tell me if I can be of any
more help to solve this issue.

Additional Information:
I am on MS Windows and I reproduced the bug with latest stable Krita 3.0 and
with Krita 3.1 Release Candidate. I did not tried any Krita 2.9.

PS:
Thanks for the great works you've done with Krita!

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to