Bug 406996 - Pen with WinTab uses coordinate relative to the top left of all displays potentially creating an offset.
Summary: Pen with WinTab uses coordinate relative to the top left of all displays pote...
Status: RESOLVED WORKSFORME
Alias: None
Product: krita
Classification: Applications
Component: Tablets (tablet issues are only very rarely bugs in Krita!) (other bugs)
Version First Reported In: 4.1.7
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL: https://youtu.be/iI8PNMCgKmo
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-28 00:03 UTC by Edward
Modified: 2024-10-19 15:07 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Edward 2019-04-28 00:03:29 UTC
Note: I'm using a Monoprice 19-Inch TFT Monitor (110707) and can't test for other graphics tablets.

STEPS TO REPRODUCE
1. Set your tablet display to be anywhere but the top left in an extended display configuration in the display settings.
1. Open Krita and use WinTab (restart Krita if you weren't already)
2. Identify whether pen pressure no longer registers or if there is an offset within the drawing area.


When using WinTab the position of the cursor inside the drawing space uses coordinate relative to the top left of all displays and puts the cursor at that position relative to the current display.

This is only within the drawing space; outside the drawing space, the system's mouse position is used.

Note: the origin is considered the top left. (hence why this is relative to the top left)

This creates an offset if you're using multiple monitors and you're drawing on one that's on the far left, but not at the top.

If you're drawing on the right display (or the offset puts the cursor outside of the drawing area), the normal coordinates are used, but pen-pressure is not used.


I would've expected Krita to be able to correct for this offset when the drawing display isn't in top left.


SOFTWARE/OS VERSIONS
Windows 10
Krita version 4.1.7

Monoprice 19-Inch TFT Monitor (110707)
Tablet Driver version 9 (2014)
Comment 1 Edward 2019-04-28 00:16:22 UTC
Video of the bug reproduced:
https://youtu.be/iI8PNMCgKmo
Comment 2 Alvin Wong 2019-04-28 09:35:42 UTC
Hi Edward, thanks for your report. I see that your bug report is filed against 4.1.7, but we've recently made some significant improvements on the tablet support so your report might no longer apply. These improvements will come with the upcoming version 4.2.0 which is set to be released around the end of May.

In the meantime, the nightly builds already contain these improvements so I would like to ask you to test it out and see whether this issue can still be reproduced. You can find the nightly builds here: https://binary-factory.kde.org/job/Krita_Nightly_Windows_Build/
Please keep in mind that the nightly builds are not of release quality and may contain bugs so they should not be used for any serious work, but only for testing.

I am guessing this is caused by a buggy driver that doesn't correctly account for multiple monitors so the new version might not actually fix the issue. However, in 4.2 there is an extra "Advanced Tablet Setting" next to the "WinTab" option that allows setting a custom tablet area mapping as an attempt to work around buggy drivers, so you could play around with that (this function also exists in 4.1.7 but is a bit hard to discover).

Please kindly test with the nightly build and let us know if it fixes the offset. If it doesn't, I would like you to obtain a tablet log to help with debugging the issue. You can obtain a tablet log by following these instructions: https://docs.krita.org/en/KritaFAQ.html#windows

By the way, I would advice you to try to look for the latest driver before testing again, since new drivers might contain fixes to the issue.
Comment 3 Bug Janitor Service 2019-05-13 04:33:08 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
mark the bug 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 4 Bug Janitor Service 2019-05-28 04:33:09 UTC
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!