https://bugs.kde.org/show_bug.cgi?id=465157
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/kwin/commit/2babccda048b |ma/kwin/commit/a6a222716833
|61305ade9046658491cfd531163 |08a193c1e886b35958038a91cad
|6 |a
--- Comment #7 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit a6a22271683308a193c1e886b35958038a91cada by Vlad Zahorodnii.
Committed on 03/02/2023 at 14:08.
Pushed by vladz into branch 'cherry-pick-2babccda'.
x11: Fix maximize animation
Window::maximize() used to be split in two halves:
- generic Window::setMaximized() and Window::maximize()
- protocol-specific Window::changeMaximize()
Window::changeMaximize() used to block all geometry updates and
Window::maximize() emit "maximize mode changed" signals. With that,
frameGeometryChanged came always before clientMaximizedStateChanged.
After merging Window::changeMaximize() and Window::maximize(), the order
of the signals has been reversed because of RAII. Unblock geometry
updates explicitly to preserve the old behavior.
(cherry picked from commit 2babccda048b61305ade9046658491cfd5311636)
M +2 -1 src/x11window.cpp
https://invent.kde.org/plasma/kwin/commit/a6a22271683308a193c1e886b35958038a91cada
--
You are receiving this mail because:
You are watching all bug changes.
