kwin/kconf_update
Nate Graham b29f211fe4 Disable translucency effect by default
Many reasons have been brought up over the years for why this effect is
not appropriate to be enabled by default:
- It was designed to highlight the whizzy technical feature of being
  able to make windows transparent, which is no longer particularly
  impressive today.
- It looks visually dated.
- It can produce a confusing visual soup by blending a window being
  moved or resized with the content below it, which we recently disabled
  for the Highlight Windows effect.
- If one window is covering up another as a way to deliberately hide the
  content of the lower window, this effect will reveal the hidden
  content whenever the upper window is moved or resized at all.

Overall it does not seem to have enough advantages to offset these
issues. Let's disable it by default--but only for the people who did not
modify its configuration at all. We can assume that those people like
it, so let's keep it on for them.

BUG: 384054
FIXED-IN: 5.23

Closes Phab task T7915
2021-05-14 15:21:11 +00:00
..
CMakeLists.txt platforms/x11: Always set swap interval to 1 2021-01-07 13:10:59 +00:00
kwin-5.16-auto-bordersize.sh
kwin-5.18-move-animspeed.py
kwin-5.21-desktop-grid-click-behavior.py Make kwin-5.21-desktop-grid-click-behavior.py use Python 3 2020-11-07 12:00:45 +00:00
kwin-5.21-no-swap-encourage.py platforms/x11: Always set swap interval to 1 2021-01-07 13:10:59 +00:00
kwin-5.23-disable-translucency-effect.sh Disable translucency effect by default 2021-05-14 15:21:11 +00:00
kwin.upd Disable translucency effect by default 2021-05-14 15:21:11 +00:00
kwinrules-5.19-placement.pl [kwinrules] Add kconf_update script to fix placement rule 2020-05-27 18:13:00 +00:00
kwinrules.upd [kwinrules] Add kconf_update script to fix placement rule 2020-05-27 18:13:00 +00:00