Because not all apps that use KConfigXT use a KCM, and I don't want to make it necessary to do so. This particular change is done with Kirogi in mind (that does not uses a KCM, and it's a pure QtQuick / Kirigami app, but uses KConfigXT) I'll add the testcase.
On Mon, 23 Dec 2019 at 03:02 Aleix Pol Gonzalez <nore...@phabricator.kde.org> wrote: > apol added a comment. View Revision <https://phabricator.kde.org/D26133> > > It could make sense to add a test. > > Also for an application (system settings or kconfig dialogs) it's already > possible to just trigger save when the kcm has changed (we already have > signals for this). Why do you think it's needed? > > *REPOSITORY* > R237 KConfig > > *REVISION DETAIL* > https://phabricator.kde.org/D26133 > > *To: *tcanabrava > *Cc: *apol, kde-frameworks-devel, LeGast00n, GB_2, michaelh, ngraham, > bruns >
