Bug 414431

Summary:	Freehand Path Tool Stopped Working With Touch Screen Of Laptop & Stylus
Product:	[Applications] krita	Reporter:	tkcammack
Component:	Tools/Freehand	Assignee:	Dmitry Kazakov <dimula73>
Status:	RESOLVED FIXED
Severity:	normal	CC:	alvin, dimula73, halla
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description tkcammack 2019-11-23 18:00:52 UTC

SUMMARY
It is difficult to explain but I will try my best. The freehand path tool is the only tool that stopped working with the touch screen feature of my laptop and stylus. The only way I can get it to work (other than with my laptops touch pad) is by hitting any of the tabs at the top of my window (ex: file, edit, view, etc.) and then if I immediately touch my canvas I can get one single stroke in. But the only way to use my freehand path tool is through this process. I rely heavily on this tool, so if I could get a fix asap, I would love that.

STEPS TO REPRODUCE
1. 
2. 
3. 

OBSERVED RESULT


EXPECTED RESULT


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

ADDITIONAL INFORMATION

Comment 1 tkcammack 2019-11-23 18:58:42 UTC

- tiar-ty and I reconfigured my krita multiple times and no resolution came out of it.
- I am using a Microsoft Surface Book 2 (a laptop that secondaries as a tablet)
- the issue happened right after a simple fix to my selection tools (I accidentally had subtract on instead of replace) after that it all went south with the freehand path tool.
- tiar-ty suggested I download and use the old version of Krita. Which I did, everything works perfect with the old Krita version.

Comment 2 Alvin Wong 2022-04-15 16:51:16 UTC

Is this issue still valid on latest release (5.0.5)?

Comment 3 Dmitry Kazakov 2022-04-18 10:52:44 UTC

I have tested the issue on Windows:

Krita 4.4.7 still has this issue
Krita 5.0.2 and master don't have this issue

So I guess it should be fixed now. Please reopen the bug if you can see the bug in the latest Krita :)