https://bugs.kde.org/show_bug.cgi?id=459820
--- Comment #2 from Sofi <koty.ve...@gmail.com> --- Ok, thank you чт, 29 сент. 2022 г., 16:17 Halla Rempt <bugzilla_nore...@kde.org>: > https://bugs.kde.org/show_bug.cgi?id=459820 > > Halla Rempt <ha...@valdyas.org> changed: > > What |Removed |Added > > ---------------------------------------------------------------------------- > Status|REPORTED |RESOLVED > Platform|Compiled Sources |Microsoft Windows > Severity|critical |normal > CC| |ha...@valdyas.org > Resolution|--- |NOT A BUG > Component|Brush engines |Tablets (tablet issues are > | |only very rarely bugs in > | |Krita!) > > --- Comment #1 from Halla Rempt <ha...@valdyas.org> --- > Hi Sofi, > > This is definitely not a bug in Krita, no matter that you only experience > this > in Krita. Tablet drivers often break for just one or two applications > because > they tend to have application-specific code. Krita, on the other hand, > doesn't > have any code that directly interfaces with the tablet drivers: we use our > development platform's abstraction layer over the operating system's > support > for tablets. > > Depending on your tablet brand, you might try to switch between the wintab > options and the windows 8 pointer api in Krita's settings, reset Krita's > settings or the settings of the tablet. > > For user support questions, please go first to https://krita-artists.org > where > other users might recognize your issues and be able to work you through a > solution for your system. > > You can also consult the manual: > https://docs.krita.org/en/user_manual/drawing_tablets.html. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
