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

            Bug ID: 393013
           Summary: Stylus can't draw once leaving tablet range with
                    "Hi-Dpi enabled" on cintiq pro 24"
           Product: krita
           Version: 4.1
          Platform: MS Windows
                OS: MS Windows
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: tablet support
          Assignee: krita-bugs-n...@kde.org
          Reporter: epixer...@gmail.com
  Target Milestone: ---

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".

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

Reply via email to