| Summary: | User configuration for KWin scripts is not applied until after disabling and reenabling the script | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Natalie Clarius <natalie_clarius> |
| Component: | kcm_kwinscripts | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | alexander.lohnau, nate, nicolas.fella, plasma-bugs-null |
| Priority: | NOR | ||
| Version First Reported In: | 5.26.4 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Natalie Clarius
2022-12-21 00:29:18 UTC
There even is a TODO for this in the code: https://invent.kde.org/plasma/kwin/-/blob/master/src/scripting/genericscriptedconfig.cpp#L182 I wonder what the best approach for this is. A brute-force approach would be to automatically reload the script when saving the config. That wouldn't require changing the scripts. Or we do what we do for scripted effects, which is a "configChanged" signal that effects connect to and re-read the config: https://invent.kde.org/plasma/kwin/-/blob/master/src/effects/scale/package/contents/code/main.js#L23 I would think that a solution that also works for existing scripts would be preferable, but I don't know what the potential drawbacks of reloading the script would be. |