The colors KCM will now call on a modified version of Breeze GTK's assets
generation script when a colorscheme is applied. This will result in a colored version
of Breeze GTK2 being generated in the user's home directory.
BUG: 412331
The colors KCM will now call on a modified version of Breeze GTK's assets
generation script when a colorscheme is applied. This will result in a colored version
of Breeze GTK2 being generated in the user's home directory.
BUG: 412331
Check that a coloured version of Breeze GTK2 is generated
whenever a colourscheme is applied.
No Linters Available |
No Unit Test Coverage |
Buildable 22451 | |
Build 22469: arc lint + arc unit |
Can you update the text plan with detailed instructions for how to make this work? It is not working for me, and with no such text plan, I don't know why.
kcms/krdb/krdb.cpp | ||
---|---|---|
992 | Instead of this, we probably want to export the KDE_INSTALL_FULL_LIBEXECDIR to C++ and use that. |
So the way forward I see as follows:
Eventually we will move stuff out of KRDB to places where it also fits in sementically. Whenever an option is changed in the kcms which call runrdb currently these things can react to that by listening to the DBus signal which is emitted currently either way now (bonus points for using KConfigWatcher).
For GTK stuff this logically would be kde-gtk-config. Since the daemon there already listens to KGlobalSettings I propose for this patch the following:
Add a new case corresponding to the color scheme change to GtkConfig::onGlobalSettingsChange inside kde-gtk-config. The lines added here can be added there as is.