https://bugs.kde.org/show_bug.cgi?id=392050
--- Comment #11 from Eike Hein <h...@kde.org> --- I can give you a general low-down of how it works, or is supposed to: In response to clicking around in the UI, the QML code in main.qml sets the new setting value in the C++ backend object (written down in launchfeedback.cpp). The C++ code receives the new value, and then updateNeedsSaving() compares it against the saved value and figures out whether it needs to mark the System Settings module as "needs saving". While a module "needs saving" the Apply button is enabled. Most likely there's a logic bug in updateNeedsSaving(). -- You are receiving this mail because: You are watching all bug changes.
