yukijoou/kwin
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
kwin/kconf_update/kwin.upd

94 lines
2.4 KiB
Text
Raw Normal View History

[effects] Drop the Scale in effect Summary: It's superseded by the new scale effect(D13461). Existing users of this effect will be migrated to the new scale effect. Depends on D13461 Reviewers: #kwin, #plasma, #vdg, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D13462
2018-06-10 11:02:57 +00:00
Version=5
# Replace old Scale in effect with Scale effect.
Id=replace-scalein-with-scale
File=kwinrc
Group=Plugins
Key=kwin4_effect_scaleinEnabled,scaleEnabled
[effects] Re-implement the Minimize Animation effect in JavaScript Summary: There were several reasons to rewrite the Minimize Animation effect in JavaScript: to simplify code and to get rid of full repaints. One could say that nothing prevents us from calculating the dirty region in postPaintScreen or postPaintWindow and it is correct, but with the scripting effects API the dirty region will be calculated for us, so we can focus more on "what we want" instead of "how". Visually, the "old" effect and the rewritten one look quite the same. Except one tiny bit: if a window doesn't have an icon in the task manager, it won't be animated. The reason for that is the purpose of this effect is to show where the window will be after it's minimized, if the window doesn't have icon in the task manager, one can't click at the center of the screen to unminimize the window. There is one significant change, the name of the effect was changed to "Squash". If we put this effect and the Magic lamp effect under "Window Minimize Animation" category (or if we add some "heading" label), then the old name and the name of the category would "conflict". The new name was suggested by Nate Graham and it very closely describes what the effect does. "Scale" doesn't fit this effect because while a window is being animated, its aspect ratio is not preserved. Reviewers: #kwin, #plasma, davidedmundson Reviewed By: #kwin, #plasma, davidedmundson Subscribers: davidedmundson, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16372
2018-09-23 17:07:48 +00:00
# Port the Minimize Animation effect to JavaScript.
Id=port-minimizeanimation-effect-to-js
File=kwinrc
Group=Plugins
Key=minimizeanimationEnabled,kwin4_effect_squashEnabled
[effects/scale] Port to JavaScript Summary: Now, when the scripting effects API has all required ingredients to port the Scale effect to JavaScript we finally can do it. The main rationale for porting this effect to JavaScript is that scripted effects API lets us focus more on what we want instead of "how". Visually, the ported version doesn't deviate from the C++ version. Test Plan: * Enable the Scale effect; * Open/close a window. Reviewers: #kwin, graesslin Reviewed By: #kwin, graesslin Subscribers: graesslin, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16478
2018-10-27 21:27:25 +00:00
# Port the Scale effect to JavaScript.
Id=port-scale-effect-to-js
File=kwinrc
Group=Effect-Scale,Effect-kwin4_effect_scale
AllKeys
Group=Plugins
Key=scaleEnabled,kwin4_effect_scaleEnabled
[kconf_update] Use scripted dim screen effect Summary: I forgot to add a kconf update that moves existing users of the builtin Dim Screen effect to the scripted version of the effect, sorry. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D16957
2018-11-17 12:14:35 +00:00
# Port the Dim Screen effect to JavaScript.
Id=port-dimscreen-effect-to-js
File=kwinrc
Group=Plugins
Key=dimscreenEnabled,kwin4_effect_dimscreenEnabled
kconfig_update for auto border size introduction Summary: If a user has set his border size explicitly in the past also respect this selection with the new auto border size mode by setting auto borders to false on update. For this a kconf_update file and a sed based shell script is added. Test Plan: Manually. Reviewers: #kwin, davidedmundson Reviewed By: #kwin, davidedmundson Subscribers: zzag, davidedmundson, kwin Tags: #kwin Maniphest Tasks: T8707 Differential Revision: https://phabricator.kde.org/D13480
2019-05-03 18:23:58 +00:00
# Deactivate auto border size if the user has changed border size in the past
Id=auto-bordersize
File=kwinrc
Group=org.kde.kdecoration2
Script=kwin-5.16-auto-bordersize.sh,sh
Migrate kwin animation speed to kdeglobals Test Plan: Tested output piping test lines into the script with different settings Removed from my kdeglobals Invoked script. New value appeared (note that if you manually test multiple times locally you have to cleanup the $version info from both kdeglobals and kwinrc or the migration will be skipped) Reviewers: zzag Reviewed By: zzag Subscribers: zzag, kwin Tags: #kwin Differential Revision: https://phabricator.kde.org/D24084
2019-09-25 13:31:52 +00:00
# Move AnimationSpeed to kdeglobals as AnimationDurationFactor converting to a useful value
Id=animation-speed
File=kwinrc,kdeglobals
Group=Compositing,KDE
Fix kwin.upd not running if python 2 not installed Summary: If the listed interpreter does not exist, kconf_update skips the update. The update script uses python3, so declare that properly. Test Plan: Saw the error by accident, it's gone now. Reviewers: #plasma, zzag Reviewed By: #plasma, zzag Subscribers: kwin, plasma-devel Tags: #kwin Differential Revision: https://phabricator.kde.org/D26942
2020-01-27 14:39:00 +00:00
Script=kwin-5.18-move-animspeed.py,python3
Allow configuring click behavior in Desktop Grid effect The following click behaviors are defined: * Switch desktop and activate window [default] * Switch desktop only The former emulates the previous default of activating clicked windows using the Present Windows effect. The latter introduces a new mode where the clicked window is not activated, allowing the user to select a virtual desktop without worrying about disrupting the last active window. The configuration toggle that controlled the use of the Present Windows effect has been subsumed into the first click behavior, i.e., if the effect is enabled, it will be implicitly triggered.
2020-10-30 09:39:00 +00:00
# In the Desktop Grid effect, replace the PresentWindows boolean with an enum
Id=desktop-grid-click-behavior
File=kwinrc
Group=Effect-DesktopGrid
Make kwin-5.21-desktop-grid-click-behavior.py use Python 3 python refers to python2, which is not desired. kwin-5.18-move-animspeed.py already uses python3.
2020-11-06 22:21:57 +00:00
Script=kwin-5.21-desktop-grid-click-behavior.py,python3
platforms/x11: Always set swap interval to 1 With the new compositing scheduling, we want the screen to be redrawn as close as possible to the next vblank. Furthermore, compositing is no longer driven by a timer. This change removes the NoSwapEncourage swap strategy as it doesn't make sense now, in addition to that it just does not work on Wayland.
2021-01-07 08:09:47 +00:00
# Remove GLPreferBufferSwap if it has a value of "n"
Id=no-swap-encourage
File=kwinrc
Group=Compositing
Fix a typo
2021-01-07 19:28:00 +00:00
Script=kwin-5.21-no-swap-encourage.py,python3
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 14:37:35 +00:00
# Make the Translucency effect disabled by default
Id=make-translucency-effect-disabled-by-default
File=kwinrc
Group=Plugins
Script=kwin-5.23-disable-translucency-effect.sh,sh
effects: Remove Flip Switch effect With the ongoing scene redesign, it needs to be rewritten. However, given that it is not used widely based on support information from various bug reports and our available man power is sparse, the most reasonable thing is to drop the effect, unfortunately.
2021-05-31 10:37:11 +00:00
# Remove the Flip Switch effect
Id=remove-flip-switch-effect
File=kwinrc
Group=TabBox,TabBoxAlternative
Script=kwin-5.23-remove-flip-switch.py,python3
effects: Remove Cover Switch effect With the ongoing scene redesign, it needs to be rewritten. However, given that it is not used widely based on support information from various bug reports and our available man power is sparse, the most reasonable thing is to drop the effect, unfortunately.
2021-05-31 10:41:05 +00:00
# Remove the Cover Switch effect
Id=remove-cover-switch-effect
File=kwinrc
Group=TabBox,TabBoxAlternative
Script=kwin-5.23-remove-cover-switch.py,python3
effects: Remove Desktop Cube Animation effect With the ongoing scene redesign, it needs to be rewritten. However, given that it is not used widely based on support information from various bug reports and our available man power is sparse, the most reasonable thing is to drop the effect, unfortunately.
2021-05-31 10:51:17 +00:00
# Remove the Desktop Cube Animation effect
Id=remove-cubeslide-effect
File=kwinrc
Group=Plugins
Script=kwin-5.23-remove-cubeslide.py,python3
Remove Xrender backend The Xrender backend was added at the time when OpenGL drivers were not particularly stable. Nowadays though, it's a totally different situation. The OpenGL render backend has been the default one for many years. It's quite stable, and it allows implementing many advanced features that other render backends don't. Many features are not tested with it during the development cycle; the only time when it is noticed is when changes in other parts of kwin break the build in the xrender backend. Effectively, the xrender backend is unmaintained nowadays. Given that the xrender backend is effectively unmaintained and our focus being shifted towards wayland, this change drops the xrender backend in favor of the opengl backend. Besides being de-facto unmaintained, another issue is that QtQuick does not support and most likely will never support the Xrender API. This poses a problem as we want thumbnail items to be natively integrated in the qtquick scene graph.
2021-06-08 18:38:43 +00:00
# Remove Backend if it has a value of "XRender"
Id=remove-xrender-backend
File=kwinrc
Group=Compositing
Script=kwin-5.23-remove-xrender-backend.py,python3
effects: Enable the scale effect by default It looks fancier than the fade effect.
2022-01-04 20:53:31 +00:00
# Enable the Scale effect by default.
Id=enable-scale-effect-by-default
File=kwinrc
Group=Plugins
Key=kwin4_effect_fadeEnabled,kwin4_effect_scaleEnabled
dynamically load effects that support edge activation effects can specify in their json file "X-KWin-Border-Activate":true and will be listed in the edge menus. Don't hardcode desktop grid and overview in the kcms
2022-05-03 16:54:36 +00:00
# Overview config group based upon plugin id
Id=overview-group-plugin-id
File=kwinrc
Options=AllGroups
Script=kwin-5.25-effect-pluginid-config-group.py,python3
Reference in a new issue Copy permalink