https://bugs.kde.org/show_bug.cgi?id=514131
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bugs.kde.org.baguette317@pa | |ssmail.net --- Comment #3 from [email protected] --- I encounter the same issue. Having to restart KWin to test each change makes writing a QML-based script an extremely unpleasant experience. In addition, this bug affects not only script developpers, but also users: they need to restart KWin for setting changes to take effect. Some popular scripts such as Krohnkite are impacted, so I wouldn't say that the impact is restricted to a niche. An ugly workaround, less disruptive than restarting KWin: before each new install, replacing the KPlugin Id by a new one in the metadata.json file seems to do the trick. $ ((N++)) $ sed -i "s/\"Id\":.*/\"Id\": \"scriptName$N\",/" /path/to/script/metadata.json $ kpackagetool6 --type=KWin/Script -i /path/to/script $ kwriteconfig6 --file kwinrc --group Plugins --key ktm$N"Enabled" true --notify $ qdbus org.kde.KWin /KWin reconfigure (One might also want to uninstall the previously installed script and to delete the corresponding configuration in ~/.config/kwinrc) -- You are receiving this mail because: You are watching all bug changes.
