Bug 484166

Summary: Make magnifying cursor look prettier when shaking it
Product: [Plasma] kwin Reporter: Elkin Cruz <linuxero789>
Component: effects-variousAssignee: KWin default assignee <kwin-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist CC: fanzhuyifan
Priority: NOR    
Version: 6.0.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Elkin Cruz 2024-03-21 14:02:17 UTC
SUMMARY

The KWin plugin "shake cursor" is pretty useful and fun to show to other people. My only gripe with it is that the strategy used to magnify the cursor makes it look ugly.

There are three ways in which I can see the cursor be magnified:
- Increase its size. Cursors are vector graphic objects so when you change its size (in settings) they appear large and slick.
- Keep its size and "zoom in" (magnify) the cursor. Depending on the interpolation strategy used, the pointer could look highly pixelated (no interpolation strategy) or look less pixelated but mushed (for example using cubic interpolation).
- Mix two previous strategies: increase size of cursor but start transition in a "zoom out" state so that the cursor starts looking the same and as it grows to its actual size it looks slick.

Regardless of the strategy used (including others that don't come to mind), I'd be nice to have a slick mouse magnification transition. Even a pixelated (no interpolation) cursor would look better, IMHO, than one that is mushed by interpolation.

Thanks :)

STEPS TO REPRODUCE
1. Activate "shake cursor" plugin in Window Manager -> Desktop Effects
2. Shake cursor

OBSERVED RESULT
Cursor is magnified and looks mushed

EXPECTED RESULT
Cursor is magnified and looks like a proper zoomed-in svg image

SOFTWARE/OS VERSIONS
Linux: Up to date Archlinux (March 21, 2024)
KDE Plasma Version: 6.0.2
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.2
Kernel version: 6.8.1-arch1-1 (64 bits)
Graphics platform: Wayland
Comment 1 fanzhuyifan 2024-03-21 16:52:36 UTC

*** This bug has been marked as a duplicate of bug 478290 ***