KConfigSkeleton::usrWriteConfig()

Andreas Pakulat apaku at gmx.de
Sun Apr 22 12:00:10 BST 2007


On 22.04.07 12:21:12, Cornelius Schumacher wrote:
> This commit 
> 
> http://websvn.kde.org/trunk/KDE/kdelibs/kdeui/config/kconfigskeleton.cpp?r1=559982&r2=560326
> 
> moved the code to write KConfigSkeleton's configuration data from the 
> writeConfig() function to the virtual usrWriteConfig() function. This broke 
> all applications which overwrote usrWriteConfig(), e.g. KOrganizer.
> 
> Is there any reason why this was done?

Thats in the commit message, the reason is to be able to completely
replace the logic that was formerly in writeConfig. And this is needed
at least in KDevelop4.

> The usrWriteConfig() function was 
> supposed to be a hook for customizations, not a function doing vital stuff. 
> Any objections to reverting that change?

Yes, as Thomas already said you can just call the base class
implementation and be done with it.

Andreas

-- 
You have a strong desire for a home and your family interests come first.




More information about the kde-core-devel mailing list