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
                   |                            |ma/plasma-workspace/commit/
                   |                            |ef57cd3d50f729f22558a20b031
                   |                            |72da539e3bb71
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #54 from Marco Martin <notm...@gmail.com> ---
Git commit ef57cd3d50f729f22558a20b03172da539e3bb71 by Marco Martin.
Committed on 23/09/2022 at 10:04.
Pushed by mart into branch 'master'.

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
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1150

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  +23   -2    components/containmentlayoutmanager/appletslayout.cpp
M  +7    -0    components/containmentlayoutmanager/appletslayout.h

https://invent.kde.org/plasma/plasma-workspace/commit/ef57cd3d50f729f22558a20b03172da539e3bb71

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to