https://bugs.kde.org/show_bug.cgi?id=494426
--- Comment #3 from Vlad Zahorodnii <vlad.zahorod...@kde.org> --- (In reply to Répási Dávid from comment #2) > When in the shake cursor effect, the cursor is locked to the "default" icon, > so only that one would need to be prerendered to a bigger size, if that is > still memory heavy, a hard cap could be introduced to the effect so no > pixelation would be seen by the user. No cap is intentional. And we're talking about an edge case, which imho is very minor. You'd need to put some real dedication to shaking the cursor in order to start observing the pixelation. > Also, just for reference, how much memory are we talking about? Atm kwin renders the cursor at approximately 250x250-300x300 size. Progressive cursor rendering can be implemented, but as of now, in comparison to the additional code, I see no strong benefits in doing it. > Have the advertised crisp look at any size It's not advertised to look crisp in **every** scenario. -- You are receiving this mail because: You are watching all bug changes.
