https://bugs.kde.org/show_bug.cgi?id=406996
Alvin Wong <al...@alvinhc.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |al...@alvinhc.com
Status|REPORTED |NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #2 from Alvin Wong <al...@alvinhc.com> ---
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.
--
You are receiving this mail because:
You are watching all bug changes.
