Bug 371689 - If "main display" is not set to monitor 1, pen pressure breaks
Summary: If "main display" is not set to monitor 1, pen pressure breaks
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.1 Beta
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-10-26 00:51 UTC by Tux Prowess
Modified: 2018-10-27 04:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Shows the display numbers, what the main display is set to, and the pen pressure problem. (246.07 KB, image/png)
2016-10-26 00:51 UTC, Tux Prowess
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tux Prowess 2016-10-26 00:51:22 UTC
Created attachment 101787 [details]
Shows the display numbers, what the main display is set to, and the pen pressure problem.

Also current with 3.0.11

If your main display is set to anything except the first monitor detected by the graphics driver, then Krita will not detect pen pressure properly and will lag as if it's working with the mouse.

This is not the fault of the tablet driver itself. Using the pen pressure test program reveals that pen pressure is fine with non-primary main displays.
Comment 1 Halla Rempt 2016-10-29 14:43:34 UTC
Hi,

This is a bit odd, because it works for my setup. I have a main monitor, a cintiq and sometimes a third monitor. Of course, sometimes Windows goes crazy and associates the tablet with the main monitor, but usually it correctly associates the second monitor with the tablet surface.

Could you perhaps create a tablet log: https://docs.krita.org/KritaFAQ#What_if_your_tablet_is_not_recognized_by_Krita.3F

And tell us exactly which brand and model your tablet is, and the version of the driver. It might also be necessary to have full information on your graphics card.
Comment 2 Andrew Crouthamel 2018-09-26 22:25:47 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 3 Andrew Crouthamel 2018-10-27 04:20:10 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!