https://bugs.kde.org/show_bug.cgi?id=446572
Nate Graham <n...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |benjamin.p...@enioka.com,
| |uhh...@gmail.com
--- Comment #2 from Nate Graham <n...@kde.org> ---
Yep, that seems to be it. The combobox gets its default value from
GtkPage::gtkThemeFromConfig()
...Which returns m_gtkConfigInterface.gtkTheme().value();
...And m_gtkConfigInterface is a DBus interface that queries org.kde.GtkConfig
/GtkConfig
So we are not going through the kconfigxt mechanism here and are implicitly
relying on the setting to have a default value from GTK-land. But it may very
well not. And it certainly won't be set to Breeze by default. I wonder how we
should fix this, though. We can't just unconditionally set Breeze to be the
default since it might not be installed. Maybe we can do that if it uses a
fallback mechanism when Breeze isn't installed?
There is also the following code:
void GtkPage::defaults()
{
Q_EMIT selectGtkThemeInCombobox(QStringLiteral("Breeze"));
}
Clicking the "Defaults" button works and resets the combobox to show Breeze.
However the button is disabled on the GTK page and does not become enabled when
you change anything on the GTK page; it only becomes enabled when something on
the other page is changed.
--
You are receiving this mail because:
You are watching all bug changes.
