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

da...@loescher.pro changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|                            |https://onedrive.live.com/v
                   |                            |iew.aspx/error-temp.pptx?ci
                   |                            |d=371a8e651305e1a7&id=docum
                   |                            |ents
                URL|https://onedrive.live.com/v |https://onedrive.live.com/r
                   |iew.aspx/error-temp.pptx?ci |edir?resid=371A8E651305E1A7
                   |d=371a8e651305e1a7&id=docum |!610999&authkey=!AGlek3kt4F
                   |ents                        |X38hI&ithint=file%2cpptx

Boudewijn Rempt <b...@valdyas.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEEDSINFO
         Resolution|---                         |WAITINGFORINFO

--- Comment #2 from da...@loescher.pro ---
Thanks for your fast reply!
But afraid not, I have added a url to a ppt with some photo's in (i use a
deliberately bad calibration to show the error). since then i have also checked
inkscape which acts the same as corel painter, so is fine.

so now i have two that work and two that don't and since krita and gimp have
almost exactly the same error wondering how you get the pen data?

--- Comment #3 from da...@loescher.pro ---
Thanks for your fast reply!
But afraid not, I have added a url to a ppt with some photo's in (i use a
deliberately bad calibration to show the error). since then i have also checked
inkscape which acts the same as corel painter, so is fine.

so now i have two that work and two that don't and since krita and gimp have
almost exactly the same error wondering how you get the pen data?

--- Comment #4 from Boudewijn Rempt <b...@valdyas.org> ---
We're just using the wintab api as described on the wacom website. N-trig pens
generally are pretty well calibrated, and this bug also doesn't sound like it's
caused by display scaling. But I still cannot reproduce the issue on my SP3,
not with 2.9, not with the 3.0 RC. Another Krita developer has an SP4 and also
doesn't have problems. Could you check with the latest RC? 

https://krita.org/item/krita-3-0-release-candidate-1-released/

We did rewrite a lot of tablet code especially because the developer with the
SP4 wanted a better experience...

--- Comment #5 from da...@loescher.pro ---
Thanks again for your reply, i've spent a few hours today trying to find some
more info. i found a few posts of people who have very similar problems, with
little or no responce, although one post on your forum said that the new
software fixed the issue - (https://forum.kde.org/viewtopic.php?f=139&t=128523)
i have aso installed photo shot like was sugested, works fin in photoshop but
still not in here.

unfortunatly this isnt't the case for me, i dled the software you linked to and
still the same issue, and as gimp has an identicle i'm wondering if it's a
wintab issue. so happy for you to mark it as fixed.

but if you have time could i ask how you calibrate your surface pen (default
windows, special software or do you just use it in it's defualt calibration)?
Also i noticed if i uninstall wintab it fixes this issue and i ink at the
calibrated point, but i lose pressure sensitivity (to be expected) and then
when re-install and the loss of calibration comes back in cirtain programs, so
am also wondering if it's a problem with my wintab instalation, so what verson
are you running - i downloaded the latest one fresh from microsoft
wintab_x64_1.0.0.20
(https://www.microsoft.com/en-us/download/details.aspx?id=49498).

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

Reply via email to