kconfig.git/autotests/kconfigskeletontest.cpp, branch v5.71.0-rc1

KConfig: Convert to SPDX license statements

2020-03-22T11:46:41+00:00

Summary:
Convert license headers to SPDX statements and add
license files as required by REUSE specification.

Reviewers: cgiboudeaux

Reviewed By: cgiboudeaux

Subscribers: ognarb, cgiboudeaux, kde-frameworks-devel

Tags: #frameworks

Maniphest Tasks: T11550

Differential Revision: https://phabricator.kde.org/D27601

Add convenience for defaults/dirty states to KCoreConfigSkeleton

2019-10-10T11:26:21+00:00

Summary:
It allows to verify if all the items of the skeleton are in their
default values or if they hold any value deviating from the latest
loaded values from KConfig.

We didn't really need this during the KCModule/QtWidgets time since we
could write KConfigDialogManager just fine without it. But for use with
QML and aiming at having similar magic in KQuickAddons::ConfigModule
such convenience functions will be needed.

Reviewers: #plasma, #frameworks, dfaure, mart

Subscribers: apol, kossebau, davidedmundson, kde-frameworks-devel

Tags: #frameworks

Differential Revision: https://phabricator.kde.org/D24494

Remove not necessary QtCore and co

2018-03-11T12:36:48+00:00

Fix some clazy warning

2017-11-30T12:36:08+00:00

autotests: fix the failures I got here.

2017-08-01T07:56:00+00:00

1) some of them can't run in parallel
2) kconfigskeletontest failed due to KSharedConfig being used under the
scene (for a year now), and there's probably some QPA or widget style
holding a ref (here, not in the CI). Indirectly, simply setting
QStandardPaths::setTestModeEnabled(true) fixes this since KSharedConfig
will then not share the instance with the non-test-mode-enabled instance.

Fix KCoreConfigSkeleton when toggling a value with saves in between

2015-01-06T23:55:00+00:00

REVIEW: 121838
Acked by Matthew Dawson

Stop re-loading values inside KCoreConfigSkeleton::save().

2014-03-28T16:08:05+00:00

The extra load of values in KCoreConfigSkeleton is not documented anywhere
that it happens, and in normal circumstances re-loading new values isn't
expecterd during a save operation.

Update various mentions of readConfig/writeConfig to read/save.

Update documentation to match the new names of functions.

Rename writeConfig() to save() and usrWriteConfig() to usrSave()

Rename functions to match the new naming conventions.  Also create old deprecated
instances of both functions to ensure that old code continues to operate
correctly.  Also make save() non-virtual, for the same reasons read() is
now non-virtual.

Rename usrReadConfig to usrRead, to be consistent with the new name for readConfig.

Rename usrReadConfig to usrRead, and mark the former as deprecated.  To maintain
compatibility, usrRead still calls usrReadConfig in its default implementation.
usrReadConfig remains empty.

REVIEW: 117010

Add KCoreConfigSkeleton::read() which doesn't call reparseConfiguration.

2014-03-23T22:00:03+00:00

Call it from generated singletons, since the constructor creates
a KConfig from a filename, which already loads from disk.
This removes the need for using DelayedParsing.

REVIEW: 116845

Code reformatted using kde-dev-scripts/astyle-kdelibs.

2013-12-18T08:53:59+00:00

Use git blame -w 867e7a5 to show authorship as it was before this commit.

Move kconfig code to the root directory.

2013-12-18T00:45:18+00:00