https://bugs.kde.org/show_bug.cgi?id=415839
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |FIXED
Latest Commit| |https://commits.kde.org/kwi
| |n/56d5f3a4f61ce00a1abc4d3c3
| |15dcbe15c22efdb
Version Fixed In| |5.18.0
Status|CONFIRMED |RESOLVED
--- Comment #26 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit 56d5f3a4f61ce00a1abc4d3c315dcbe15c22efdb by Vlad Zahorodnii.
Committed on 03/02/2020 at 11:56.
Pushed by vladz into branch 'Plasma/5.18'.
[x11] Fix visual artifacts during interactive resize
Summary:
When a window is being interactively resized, its contents may jump. The
reason why that happens is because KWin renders partially resized client
window. Composite extension spec says that a window will get a new pixmap
each time it is resized or mapped. This applies to the frame window, but
not to the client window itself. If the client window is resized,
off-screen storage for the frame window won't be reallocated. Therefore,
KWin may render partially resized client window if the client doesn't
attempt to be in sync with our rendering loop. Currently, the only way
to do that is to use extended frame counters, which are not supported by
KWin.
So, in order to fix visual artifacts during interactive resize, we need
somehow forcefully re-allocate off-screen storage for the frame window.
Unfortunately, Composite extension doesn't provide any request to do
that, so the only option we have is to resize the frame window.
FIXED-IN: 5.18.0
Reviewers: #kwin
Subscribers: davidedmundson, ngraham, alexde, fredrik, kwin
Tags: #kwin
Differential Revision: https://phabricator.kde.org/D26914
M +11 -1 scene.cpp
M +2 -1 scene.h
M +1 -1 toplevel.cpp
M +39 -13 x11client.cpp
M +2 -0 x11client.h
https://commits.kde.org/kwin/56d5f3a4f61ce00a1abc4d3c315dcbe15c22efdb
--
You are receiving this mail because:
You are watching all bug changes.
