https://bugs.kde.org/show_bug.cgi?id=413645
Aaron Rainbolt <arraybo...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/plasma-desktop/commit/22 |ma/plasma-workspace/commit/
|fa69d96d64422318e83cc57d9ed |0a01c8910309fb9f289fe0aa584
|1d0a08c17b0 |92e106d154548
--- Comment #64 from Aaron Rainbolt <arraybo...@gmail.com> ---
Git commit 0a01c8910309fb9f289fe0aa58492e106d154548 by Aaron Rainbolt, on
behalf of Marco Martin.
Committed on 13/10/2022 at 21:45.
Pushed by ngraham into branch 'Plasma/5.24'.
Introduce a lock that blocks relayouts and config writes
The resize of the layout area can happen either by screen resolution
change or available screen area change (a panel appears or is resized)
This is not an atomic operation, as width and height are usually set in
2 different operations, and even worse the layout area is resized to
match the available one with an animation, so many intermediate resizes
that should never cause a relayout happen.
In normal operation an event compression timer limits the actual
relayouts to hopefully one, but if the system is really slowed down
(for instance, startup) the timer may expire and cause relayouts in
non useful sizes, losing the needed configuration
In combination with
The lock blocks all relayout and config writes when the size of the
layout area doesn't correspond to corona availablescreenrect, which are
the only "settled" cases.
M +24 -2 components/containmentlayoutmanager/appletslayout.cpp
M +7 -0 components/containmentlayoutmanager/appletslayout.h
https://invent.kde.org/plasma/plasma-workspace/commit/0a01c8910309fb9f289fe0aa58492e106d154548
--
You are receiving this mail because:
You are watching all bug changes.
