b29f211fe4
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
23 lines
539 B
Bash
23 lines
539 B
Bash
#!/bin/sh
|
|
|
|
HAS_ENABLED_KEY=''
|
|
HAS_CUSTOM_CONFIG=''
|
|
|
|
kwinrcname=`qtpaths --locate-file GenericConfigLocation kwinrc`
|
|
if [ -f "$kwinrcname" ]; then
|
|
if grep -q "\[Effect-kwin4_effect_translucency\]" "$kwinrcname"; then
|
|
HAS_CUSTOM_CONFIG=1
|
|
fi
|
|
fi
|
|
|
|
while read -r line; do
|
|
KEY="${line%=*}"
|
|
if [ "$KEY" == "kwin4_effect_translucencyEnabled" ]; then
|
|
HAS_ENABLED_KEY=1
|
|
fi
|
|
echo "$line"
|
|
done
|
|
|
|
if [ -n "$HAS_CUSTOM_CONFIG" ] && [ -z "$HAS_ENABLED_KEY" ]; then
|
|
echo "kwin4_effect_translucencyEnabled=true"
|
|
fi
|