Bug 362933 - [WACOM] Krita paint stroke with tablet can only use left-top-corner of screen, offset with a factor of 1/2 or 1/4
Summary: [WACOM] Krita paint stroke with tablet can only use left-top-corner of screen...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (show other bugs)
Version: 3.0 Beta
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-11 10:16 UTC by jonatan
Modified: 2016-05-26 14:03 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot of bug at 1920x1080 resolution (146.92 KB, image/jpeg)
2016-05-11 10:18 UTC, jonatan
Details
screenshot of bug at 4k resolution (468.90 KB, image/jpeg)
2016-05-11 10:23 UTC, jonatan
Details
log of drawing (849.12 KB, text/plain)
2016-05-11 10:24 UTC, jonatan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jonatan 2016-05-11 10:16:59 UTC
When using my tablet with the beta builds the painting happens at the left-top part of screen only. It seems the pen position is mapped to only the left-top corner of the screen. When working at 1920x1080 it is 1/2 the width and 1/2 the height, when working with 4x resolution it seems to be about 1/4 the width and height.

Works: 
2.9, 
krita3-prealpha3-de0d43d
Does not work: 
krita-3.0-Beta-master-962bfe1-x64
krita-3.0-Beta-master-4a58260-x64
krita-master-f38b47e-x64

Reproducible: Always

Steps to Reproduce:
1. Open Krita
2. New image
3. Paint using pen



Painting with mouse works
Controlling GUI widgets and color picker with pen works
Right-click circular menu appears at the wrong position as well when using pen
Comment 1 jonatan 2016-05-11 10:18:02 UTC
Created attachment 98906 [details]
screenshot of bug at 1920x1080 resolution
Comment 2 jonatan 2016-05-11 10:23:43 UTC
Created attachment 98907 [details]
screenshot of bug at 4k resolution
Comment 3 jonatan 2016-05-11 10:24:16 UTC
Created attachment 98908 [details]
log of drawing
Comment 4 jonatan 2016-05-11 10:30:21 UTC
After some more investigation, it seems it is using the top left approximately 700x480 pixels. Could be related to tablet resolution? 
I am using a Wacom Bamboo Fun Pen & Touch Medium
Comment 5 Halla Rempt 2016-05-11 10:30:39 UTC
Hi Jonathan,

Which tablet do you use? And do you have display scaling enabled in Windows?
Comment 6 Halla Rempt 2016-05-11 10:59:45 UTC
The really interesting thing is that only the version that uses Qt's hidpi awareness seems to map correctly for you. That's extra-double-plus strange, because setting the display scaling in Windows doesn't make any difference for me on my SP3...
Comment 7 jonatan 2016-05-11 11:28:01 UTC
I am using display scaling of 125%

A more precise measurement suggests that only the topleft 640x480 area is used.
Comment 8 Halla Rempt 2016-05-12 15:25:01 UTC
Weird... I just put my SP3 at 125% scaling, and everything worked fine (but that's with the built-in ntrig pen + wintab driver, so it's not exactly comparable...) Can you try to generate a tablet log as per https://docs.krita.org/KritaFAQ#Tablets ?
Comment 9 Halla Rempt 2016-05-14 09:32:03 UTC
I suspect that this commit causes the issue:


commit 23596b92c5f1ad05379ac4e7f65a1350a6e5f2ba
Author: Michael Abrahams <miabraha@gmail.com>
Date:   Tue Mar 15 09:40:48 2016 -0400

    Support DPI switching in Wintab coordinate scaling
    
    Read current DPI from qApp->activeWindow->devicePixelRatio()
Comment 10 jonatan 2016-05-17 07:39:51 UTC
(In reply to Boudewijn Rempt from comment #8)
> Weird... I just put my SP3 at 125% scaling, and everything worked fine (but
> that's with the built-in ntrig pen + wintab driver, so it's not exactly
> comparable...) Can you try to generate a tablet log as per
> https://docs.krita.org/KritaFAQ#Tablets ?

I have added a log as attachment. ("log of drawing")
Comment 11 jonatan 2016-05-26 13:54:59 UTC
For me it works fine now, not only in the newest build but also in the builds mentioned in this bug. Maybe it was fixed by a windows update???
Comment 12 Halla Rempt 2016-05-26 14:03:07 UTC
That is not entirely inconceivable, since the converse happens all the time as well :-)