kconfig.git/autotests/kconfigskeletontest.cpp, branch v5.40.0-rc1 hurd kconfig.git autotests: fix the failures I got here. 2017-08-01T07:56:00+00:00 David Faure faure@kde.org 2017-08-01T07:56:00+00:00 48e2e7c9bcd24cc010a6af0a455f8793ea863d40 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. 
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 Albert Astals Cid aacid@kde.org 2015-01-06T23:54:10+00:00 257b66e049483d198723e515c3c1e65e18b6afb3 REVIEW: 121838 Acked by Matthew Dawson 
REVIEW: 121838
Acked by Matthew Dawson
Stop re-loading values inside KCoreConfigSkeleton::save(). 2014-03-28T16:08:05+00:00 Matthew Dawson matthew@mjdsystems.ca 2014-03-28T15:59:51+00:00 4846b50aea0bc2262238963a85ab3556c22412e4 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 
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 David Faure faure@kde.org 2014-03-16T22:30:59+00:00 c1980dbc51c9aa2770d09850e69529ea2211924b 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 
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 David Faure faure@kde.org 2013-12-18T08:53:59+00:00 159963832457e6307282308455330acc7b5bd153 Use git blame -w 867e7a5 to show authorship as it was before this commit. 
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 Jenkins CI null@kde.org 2013-12-18T00:45:18+00:00 867e7a50e6396338ab4fe9aa22ad141e4cd344d2