Bug 393013

Summary:	Stylus can't draw once leaving tablet range with "Hi-Dpi enabled" on cintiq pro 24"
Product:	[Applications] krita	Reporter:	epixerion
Component:	Usability	Assignee:	Krita Bugs <krita-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	alvin, halla
Priority:	NOR	Keywords:	triaged
Version:	4.0.1
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:
Attachments:	LOG file log without hi-dpi

Description epixerion 2018-04-11 16:05:23 UTC

on krita 4.0 and 4.1 on windows 10 using a cintiq pro 24"

Overview :

this bug only occur if krita is on 'enable Hi-dpi support'

what happen is once a brush stroke have been made on the canvas, once the stylus leave the tablet stylus detection area ( that mean as long as I keep hovering the canvas, I can still draw) I cannot re-enter the canvas with the stylus, I basically cannot brush anymore. 
if the stylus re-enter an UI part of krita (not the canvas), krita detect the stylus again and I can keep drawing on the canvas ( assuming I hovered back into the canvas from the UI without leaving the stylus detection).

step to reproduce :

1) create a blank document 
2) start drawing with stylus (keep hovering the tablet without loosing connection
3) once connection with stylus is loss, can't draw anymore
4) move stylus to krita UI (non canvas area)
5) hover back to canvas and keep drawing

Actual Results :
drawing again after the stylus lost connection with cintiq don't work.

Expected Results :
moving stylus back into on the tablet in the canvas area should lets us draw without having to move into UI frist.

Build Date & Plateform : 
happen krita 4.0.0, 4.0.1, 3.3.2 On windows 10

Additional Information:

this is a bug I also had about 3 year ago on a complete different machine and OS with a simple bamboo pen & touch, I didn't continued using krita since then because of that.

a 'RESOLVED' bug closely related to it is "340684".

Comment 1 Halla Rempt 2018-04-11 17:27:42 UTC

Thanks for making the report!

Comment 2 Alvin Wong 2018-04-11 18:46:07 UTC

I think I would really need a tablet log for this... please get a tablet log: https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F

Comment 3 epixerion 2018-04-11 20:11:34 UTC

Created attachment 111959 [details]
LOG file

The  "[BLOCKED 2:] line happen when stylus re-enter tablet detection range

Comment 4 Alvin Wong 2018-04-12 02:47:45 UTC

The issue you have is that no tablet events are being sent to the
Krita canvas at all, so even when you can draw it has no pressure
sensitivity at all and thus cannot be considered to be working
properly.

Can you get a tablet log when Hi-DPI is switched off in Krita? I
cannot tell if it is even working at all.

Comment 5 epixerion 2018-04-12 07:35:21 UTC

Created attachment 111963 [details]
log without hi-dpi

you're right, I was so focused on the stylus stopping working that I haven't noticed there was no pressure sensitivity.

Comment 6 Halla Rempt 2018-04-28 10:31:33 UTC

Did you manage to get it working either with Wacom drivers correctly installed or with Windows Ink?

Comment 7 epixerion 2018-04-28 13:58:57 UTC

no matter which setup I tried, with hi-dpi enabled, it just won't work.

Comment 8 Alvin Wong 2018-05-13 11:25:01 UTC

May I ask what values are shown and what setting is enabled on the screen resolution dialog, which is the dialog that pops up when hovering the tablet stylus over the Krita window with Shift pressed down?

Comment 9 Andrew Crouthamel 2018-09-28 03:31:04 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 10 Andrew Crouthamel 2018-10-29 02:15:59 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!