https://bugs.kde.org/show_bug.cgi?id=413645
Marco Martin <notm...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/plasma-workspace/commit/ |ma/plasma-desktop/commit/bd
|ef57cd3d50f729f22558a20b031 |676333cf57659bc885928afe5d3
|72da539e3bb71 |fe908589e79
--- Comment #55 from Marco Martin <notm...@gmail.com> ---
Git commit bd676333cf57659bc885928afe5d3fe908589e79 by Marco Martin.
Committed on 23/09/2022 at 10:05.
Pushed by mart into branch 'master'.
Use relayout locking
This makes use of the layout locking freature introduced in
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2120
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.
A 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.
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 +1 -0 containments/desktop/package/contents/ui/main.qml
https://invent.kde.org/plasma/plasma-desktop/commit/bd676333cf57659bc885928afe5d3fe908589e79
--
You are receiving this mail because:
You are watching all bug changes.
