https://bugs.kde.org/show_bug.cgi?id=527478
Vlad Zahorodnii <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Latest Commit| |https://invent.kde.org/plas | |ma/kwin/-/commit/80d7a91c8b | |50b949bf480457c7403ce91727c | |694 Status|ASSIGNED |RESOLVED --- Comment #14 from Vlad Zahorodnii <[email protected]> --- Git commit 80d7a91c8b50b949bf480457c7403ce91727c694 by Vlad Zahorodnii. Committed on 21/10/2026 at 13:53. Pushed by vladz into branch 'master'. plugins/slidingnotifications: Fix instant animation speed handling The old configs can contain AnimationDurationFactor values such as 0.08838834764831843. This is leftover from the old KCM behavior. The current system settings allow to set animation speed in more granular steps, e.g. 0, 0.5, 0.75, etc. Such very small animation duration factors can result in spring constants that makes the `fade` SpringMotion unstable. With very high spring constants, the fade SpringMotion can output opacities such as -9.28451e+293 -8.35006e+293 -7.51106e+293 -6.75813e+293 -6.07794e+293 This change makes the slide notifications effect sanitize the duration factors to make sure that the computed spring constants won't make the SpringMotion unstable. It also adds relevant guards to avoid creating animations in the first place if the "instant" animation speed has been configured. M +26 -2 src/plugins/slidingnotifications/slidingnotifications.cpp https://invent.kde.org/plasma/kwin/-/commit/80d7a91c8b50b949bf480457c7403ce91727c694 -- You are receiving this mail because: You are watching all bug changes.
