KConfig + KComponentData (Re: KInstance redesign)
kloecker at kde.org
Tue Jan 23 20:02:51 GMT 2007
On Sunday 21 January 2007 12:58, Matthias Kretz wrote:
> On Sunday 21 January 2007 12:09, Matthias Kretz wrote:
> > not necessary, but nice IMHO (This would break _a lot_ of code. I'm
> > not sure it's worth it):
> > - remove the ::Ptr part of KSharedConfig and make it explicitly
> > shared (well, detaching doesn't make much sense for KSharedConfig,
> > though, no?) - make KConfig an explicitly shared class but
> > different from KSharedConfig in that multiple (different/detached)
> > objects may reference the same config file with the in memory
> > reprensentation not having to be the same.
> another idea:
> make KConfig implicitly shared where detaching only detaches the
> currently set group. This way the in memory representation of one
> config file is always shared while different KConfig objects of the
> same config file don't change each others group with setGroup.
> Calling setGroup would implicitly detach...
setGroup? Has this method (with its nasty side-effect) not been
obsoleted already long ago by KConfigGroup?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel