[DEV]: Remove the necessity to restart KWin to test newer version of the script

[gikari]

Summary

KWin caches the script and, because of that, it does not load a newer version once it's installed. Either we need to:

1. Fix this issue in the upstream
2. Find a way to work around the issue

Additional info

No response

[ikajdan]

Would qdbus-qt5 org.kde.KWin /KWin reconfigure work in that case?

[gikari]

Would qdbus-qt5 org.kde.KWin /KWin reconfigure work in that case?

Our KCM unloads Bismuth and then loads all the enabled KWin scripts again, calling KWin DBus methods. What I tried:

1. Change the sources, so that a new random string is printed on script launch.
2. Disable Bismuth KWin Script part from KCM.
3. Enable it from there.

Result: no new string is printed.

1. Same
2. Disable Bismuth from KCM
3. Call the "reconfigure" KWin method
4. Enable Bismuth from KCM

Result: no new string is printed.

1. Same
2. Call the "reconfigure" KWin method
3. Disable Bismuth from KCM
4. Enable Bismuth from KCM

Result: no new string is printed.

So, the conclusion is that this approach does not work.

[gikari]

Reported an issue upsteam: https://bugs.kde.org/show_bug.cgi?id=445839