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-workspace/commit/ |ma/plasma-desktop/commit/23
|0a01c8910309fb9f289fe0aa584 |4cd860532449f017ecbbca6a8ca
|92e106d154548 |ad5473fcf8b
--- Comment #65 from Aaron Rainbolt <arraybo...@gmail.com> ---
Git commit 234cd860532449f017ecbbca6a8caad5473fcf8b by Aaron Rainbolt, on
behalf of Marco Martin.
Committed on 13/10/2022 at 21:46.
Pushed by ngraham into branch 'Plasma/5.24'.
Use relayout locking
This makes use of the layout locking freature introduced in
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 +3 -2 containments/desktop/package/contents/ui/main.qml
https://invent.kde.org/plasma/plasma-desktop/commit/234cd860532449f017ecbbca6a8caad5473fcf8b
--
You are receiving this mail because:
You are watching all bug changes.
