Hello!

I'm on a "penabled" Lenovo machine (Yoga 720 w. Wacom digitizer built in) running Windows.

I'm suddenly having this odd issue that I didn't use to have when using the pen:

If "Enable Touch Painting" under Configure/Tools is on, everything works fine. Pen pressure, clicks, the works. But I get strokes once in a while from my palm. Which is why I prefer setting "Enable Touch Painting" off.

If I set it to off, however, Krita has started not getting "pen-up" events. Meaning, I draw a stroke, end it, lift the pen. Then, the stroke doesn't end, I can't use eyedropper or change stroke color. Also, if I lift the pen and move the mouse, I'll get lines at 100% pressure relative to the last point I touched the pen. To get Krita to register a stroke end, I then have to click the mouse.

Again, it seems that the digitizer somehow sends pressure 0% - there's no visible effects of drawing happening at that point - but that the "pen-up" event doesn't fire.

Artrage, Mischief, Affinity Photo, Blender all work as expected with the digitizer. I don't know if my Windows or Wacom settings have changed, but again, other applications work fine.

Any ideas?

Does it matter whether you enable Windows 8 Pointer API in Krita's settings?

Vert wrote:If I set it to off, however, Krita has started not getting "pen-up" events. Meaning, I draw a stroke, end it, lift the pen. Then, the stroke doesn't end, I can't use eyedropper or change stroke color. Also, if I lift the pen and move the mouse, I'll get lines at 100% pressure relative to the last point I touched the pen. To get Krita to register a stroke end, I then have to click the mouse.

This sounds like the exact issue that I personally fixed in Krita 3.3.2 specifically for WIndows 10 ver 1709 (aka Fall Creators update). Have you tried updating Krita?

alvinwong, you are correct. Thanks for fixing this issue! No surprise that "creator's update" brings issues.

I'd normally not forum post without trying stuff like upgrading first. To explain myself, I've been working around this issue for a while. I was certain it was just last week that I tried both up- and downgrading, but it can't have been seeing as 3.3.2 is from Nov 3.

Anyways, sorry for the confusion and thanks for your work.