Commit 69b756e2 authored by David Redondo's avatar David Redondo 🏎
Browse files

Don't set a new palette if the application has a custom color scheme set

Summary:
If an application has explicitly set a custom color scheme we shouldn't change
the palette when the global color scheme changes because it explicitly wants to
use its custom one. For the same reason we already don't update the titlebar
color to the global one if this property is set.

Test Plan:
Change colorscheme in kate or kcolorschemedemo and change  the global
one in the colors kcm.

Reviewers: #plasma, ngraham

Reviewed By: ngraham

Subscribers: plasma-devel

Tags: #plasma

Differential Revision: https://phabricator.kde.org/D25915
parent 945abb25
......@@ -268,6 +268,10 @@ void KHintsSettings::slotNotifyChange(int type, int arg)
switch (type) {
case PaletteChanged: {
// Don't change the palette if the application has a custom one set
if (!qApp->property("KDE_COLOR_SCHEME_PATH").toString().isEmpty()) {
break;
}
loadPalettes();
//QApplication::setPalette and QGuiApplication::setPalette are different functions
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment