Can't tell if lazy programming or just figuring it will fix itself. In theory there would be a point of overflow maybe? Well, I guess that also fixes itself.

[–] [email protected] 13 points 4 days ago

It's by design as mentioned in this bug report.

There is a hidden config to cap the over magnification on shake

[Effect-shakecursor]
OverMagnification=0

[–] [email protected] 4 points 4 days ago (2 children)

I assume the KDE implementation resizes to default when you stop shaking it.

I could totally see someone coding a function that increases the mouse pointer by x% every y mouse shakes, and then neglecting to put in a size cap.

[–] moonpiedumplings 4 points 4 days ago* (last edited 4 days ago) (1 children)

I could totally see someone coding a function that increases the mouse pointer by x% every y mouse shakes, and then neglecting to put in a size cap.

This feature used to be in KDE 5 as well though, but with a size cap. I suspect the removal of the size cap is intentional rather than a bug.

[–] [email protected] 1 points 1 day ago

Having a size cap does not make much sense since the increased pointer size is triggered intentionally, meaning if someone keeps shaking the pointer, they must want it bigger (whether for amusement or because they're hella blind).

[–] [email protected] 1 points 4 days ago

Yes, it resets once motion is stopped. It's one of those things where without comments in the code or something you could also assume forgetting to check one of the bounds just happened to work fine.