Anyone knows why KCoreConfigSkeleton::writeConfig is void?

It can obviously fail, I just had a bug report from a user that could not 
write to his config file in Okular because somehow he had set it to read only 
and very weird things were happening.

But if it is void there is no way for me to know if it succeeded or not.

Maybe we can change it to bool in frameworks?

Cheers,
  Albert

Reply via email to