https://bugs.kde.org/show_bug.cgi?id=398899

David Edmundson <k...@davidedmundson.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|CONFIRMED                   |RESOLVED
      Latest Commit|                            |https://commits.kde.org/kwa
                   |                            |yland-integration/0a0c3f23f
                   |                            |ce265f36e5b8fb2b4b8bd311c7c
                   |                            |1beb

--- Comment #7 from David Edmundson <k...@davidedmundson.co.uk> ---
Git commit 0a0c3f23fce265f36e5b8fb2b4b8bd311c7c1beb by David Edmundson.
Committed on 02/05/2019 at 08:44.
Pushed by davidedmundson into branch 'master'.

Track surface creation/destruction inside wayland window effects

Summary:
The wayland surface is destroyed and recreated after every hide/show. As
it's a new surface, it needs a new blur attached and applied.

The best hook is the expose event on the window.

The current event filtering in Breeze operates on the QWidget which
doesn't match the window. Fixing there still introduces a second layer
of event filters on another object once the window is known.

Whilst it could be done in breeze, clients should ideally just call
KWindowEffects once per window and forget about it regardless of
the underlying state. It also fixes all other wayland users of the call
at once.

This fixes blur on context menus opened a second time.

Test Plan:
Turned on the show transparency effect in breeze
Opened a context menu multiple times
Observed that it was transparent and blurred

Reviewers: #kwin

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D20951

M  +109  -4    src/windowsystem/windoweffects.cpp
M  +22   -2    src/windowsystem/windoweffects.h

https://commits.kde.org/kwayland-integration/0a0c3f23fce265f36e5b8fb2b4b8bd311c7c1beb

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

Reply via email to