kconfig.git - hurd kconfig.git

Age	Commit message (Collapse)	Author
2017-01-16	Prefer nullptr over Q_NULLPTR	Kevin Funk

2016-04-16	kconfigcompiler_test_signals.cpp - pedantic	Allen Winter

2015-12-23	Fix some Clazy warnings	Imran Tatriev

2014-09-18	Replace nullptr with Q_NULLPTR.	Nicolás Alvarez
	gcc 4.5 doesn't have nullptr.
2014-03-28	Stop re-loading values inside KCoreConfigSkeleton::save().	Matthew Dawson
	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
2014-02-20	Make kconfig_compiler signals actually useful + add unit test	Alex Richardson
	Previously the classes generated by kconfig_compiler would only emit the defined signals when using the setters provided by that class. However, when using e.g. KConfigDialog which uses KConfigSkeletonItem::setProperty() to change the items no signal was generated. This patch fixes this by using a wrapper KConfigSkeletonItem subclass that calls a private itemChanged() method in the generated class which updates the set of changed properties. As soon as the item is saved (usrWriteConfig() in the generated class is called) the signal will be emitted REVIEW: 115635 REVIEW: 115634