There is a minor problem still remaining with windows maximized on multiple monitors. You can see it occurring several times in the video attached to bug #348121. Sometimes, there is a weird animation when restoring the window to normal size, where the window flies in from the side of the screen. (I'm assuming this is not intentional.) Reproducible: Always Steps to Reproduce: 1. Drag a window to the top of the second monitor to maximize it. 2. Drag it downward to unmaximize it. Actual Results: The window flies in rapidly from the right-hand edge of the screen. Expected Results: The window should animate from its current maximized position.
Git commit 595c5937c9a1e13bdeed2759034ed66d8c89d614 by Marco Martin. Committed on 04/03/2016 at 17:19. Pushed by mart into branch 'master'. use a global static for animation ids using stack adresses makes it possible (even tough not frequent) for two animations (onle just killed, one just created) to have the same id, causing scripts to be potentially really confused. this replaces the id with a global counter, and the "flying tooltips" bug is gone. REVIEW:127276 Related: bug 360068 M +2 -0 libkwineffects/anidata_p.h M +8 -4 libkwineffects/kwinanimationeffect.cpp http://commits.kde.org/kwin/595c5937c9a1e13bdeed2759034ed66d8c89d614
Git commit a9fad7396e30a380a27090538e7e66dec6984c52 by Martin Gräßlin, on behalf of Marco Martin. Committed on 23/03/2016 at 11:03. Pushed by graesslin into branch 'Plasma/5.6'. use a global static for animation ids using stack adresses makes it possible (even tough not frequent) for two animations (onle just killed, one just created) to have the same id, causing scripts to be potentially really confused. this replaces the id with a global counter, and the "flying tooltips" bug is gone. REVIEW:127276 Related: bug 360068 M +2 -0 libkwineffects/anidata_p.h M +8 -4 libkwineffects/kwinanimationeffect.cpp http://commits.kde.org/kwin/a9fad7396e30a380a27090538e7e66dec6984c52
This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number.