[Konsole-devel] [konsole] [Bug 198175] Konsole should set blur region for the new kwin effect

Eike Hein hein at kde.org
Sun Sep 15 19:56:51 UTC 2013


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

--- Comment #48 from Eike Hein <hein at kde.org> ---
Here's useful background for sandsmark's patch, which was the result of some
discussion on #kde-devel yesterday:

1) It was decided that whether blur should occur or not has to be optional, and
that the option should be placed in the profile appearance options with the
existing options for translucency and background coloring. This fits the
application design and also answers the concern that blur is sometimes
desirable and sometimes not, allowing users to set up separate profiles for
each and spawn terminals using either as desired.

2) The above implies that the terminal widget has to update the blur region as
its geometry (position, size) and visibility changes, since there can be
multiple widgets in the window (tabs, splits). The ideal outcome is to assemble
the union of all the desired blur regions in the window whenever needed and
commit them atomically to the prop. A difficulty here with every widget
removing its own blur region and writing its new blur region itself is that you
get into ordering problems around overlaps.

3) Since the terminal widget can be embedded into other codebases via the KPart
component, it also has to interact with possible blur regions set elsewhere in
the window by foreign code, further complicating the above. On top of that,
with kdelibs feature-frozen, merging any solution into the libs might not be
possible.

4) Martin's results so far seem to indicate that kwin doesn't notice change to
the property in realtime.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the konsole-devel mailing list