https://bugs.kde.org/show_bug.cgi?id=455570
stephen <tgdev...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WAITINGFORINFO |---
Status|NEEDSINFO |REPORTED
--- Comment #29 from stephen <tgdev...@gmail.com> ---
(In reply to Dmitry Kazakov from comment #27)
> Hi, Stephen!
>
> > [...] the brush outline cursor would be best if :
> > A. it was as fast as the system cursor
>
> It is technically impossible to make the brush outline to be as fast as the
> system cursor. The outline of the brush will always be slower than the
> cursor. The reason is easy: the cursor is painted with a special fast-path
> routine by hardware. And the brush outline is painted by software alongside
> the canvas painting. We can make it "faster" to some extent, but it will
> always be several frames slower than the hardware cursor.
>
> > its color was only shifting between black/white, and stays correctly
> > visible no matter the color on the canvas.
>
> That's a different issue, let's not drift from the main topic :)
>
> For Stephen and Protoniv:
>
> I'm afraid I cannot reproduce the regression you report. I tried the two
> brushes described by Protoniv and both of them work fine with with mouse,
> stylus+winink, stylus+wintab on Windows.
>
> The video on the forum looks as if Krita has the "Thread limit" set to '1'
> in the performance preferences. Could you try resetting Krita settings and
> recheck?
>
> https://docs.krita.org/en/KritaFAQ.html#resetting-krita-configuration
Hello Dmitry.
So, I've reset my settings as suggested, but using the stylus, it's the same.
On my side, the cursor gets stuck while painting with stylus+Wintab and
stylus+WinInk.
--
You are receiving this mail because:
You are watching all bug changes.
