Changes into KConfigSkeleton between kde3.x and kde4.0

[Andreas Pakulat]

On 16.05.07 23:00:07, Laurent Montel wrote:
> Before it was:
> 
> KConfigSingleton::writeConfig()
> {
> ....
>    save_data_from_kconfigSingleton ;
> ....
>    and after call: usrWriteConfig();
> }
> 
> usrWriteConfig() is a virtual function.
> 
> 
> After into kde4.0 we have:
> KConfigSingleton::writeConfig()
> {
>     call: usrWriteConfig();
> }
> 
> void KConfigSingleton::usrWriteConfig()
> {
>   save_data_from_kconfigSingleton();
> }
> 
> So now data was not stored when we call writeConfig and redefine virtual 
> function "usrWriteConfig()"
> 
> For me it's a bug.

For me its just a behavioural change. And its needed for some use-cases,
for example in KDevelop where the KConfigSkeleton's "default" way of
storing things into the kconfig object doesn't work. So this change
allows users of KConfigSkeleton to do more customization.

Instead you can just call the default implementation before or after you
did your own stuff, so I don't see a problem.

Andreas

-- 
Your sister swims out to meet troop ships.