Bug 389247

Summary:	Cursor will not move brush stroke
Product:	[Applications] krita	Reporter:	Harriet <harrietmaclennan>
Component:	Brush engines	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	alvin, halla, Soufragie
Priority:	NOR	Keywords:	triaged
Version First Reported In:	3.3.3
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Harriet 2018-01-20 11:33:51 UTC

I updated by windows microsoft surface tablet and it seems to have updated Krita and now when I open Krita no brush strokes work - I cannot use the fill feature, when i put my cursor onto the screen it shows up however when I drag it across the screen it does not move and no colour appears. Also the icons in my tool bar are massive and I am not sure how to change them. Also is Kriat known to make surface pro screens flicker? Thanks Harriet

Comment 1 Alvin Wong 2018-01-20 12:53:01 UTC

Try going to Settings -> Configure Krita, and in Tablet settings, select the Windows 8+ Pointer Input option.

Comment 2 Harriet 2018-01-20 12:57:07 UTC

I have figured out it only works when I “enable touch painting” which is not ideal. Is there a way of having it working and I can uncheck the enable touch painting box? The solution you have given me did not work.

Comment 3 Alvin Wong 2018-01-20 17:44:14 UTC

Are you using an N-Trig stylus (e.g. surface pen) or a capacitive touchscreen stylus? if you use a capacitive touchscreen stylus it will be the same as using your finger, thus requiring touch painting to be enabled.

Comment 4 Harriet 2018-01-20 20:22:33 UTC

I am using a Surface Pen. The app was working perfectly (I had disabled touch painting and there was no issue months back) until I updated my windows and now the cursor will not draw when I disable it.

Comment 5 Alvin Wong 2018-01-21 06:35:17 UTC

Then there is no way that enabling Windows 8+ Pointer Input would not fix the issue. Have you restarted Krita after enabling it?

Comment 6 Halla Rempt 2018-01-24 09:24:27 UTC

Status update.

Comment 7 Andrew Crouthamel 2018-09-28 03:22:56 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Andrew Crouthamel 2018-10-29 01:59:39 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!