On Thursday 26 July 2001 15:51, Marc Mutz wrote:
> On Wednesday 25 July 2001 19:28, David Faure wrote:
> > On Wed, Jul 25, 2001 at 07:40:18AM -0700, Charles Samuels wrote:
> > > In addition to Rob's comments, we should eliminate the obvious lack
> > > of OO safety in KConfig and always explicitly set a group when
> > > accessing a key.
> > >
> > > My personal favorite way is a group(QString) function that returns
> > > a temporary KConfigGroup.
> > >
> > > In other words
> > >
> > > config->group("Some Group Name")->readEntry("Some Key");
> >
> > This is an excellent, excellent idea.
> <snip>
> 
> I wonder if you have come across KConfigGroupSaver? ;-)

Of course I have. KConfigGroupSaver is an ugly workaround for this API problem,
it's not a proper OO solution.

-- 
David FAURE, david@mandrakesoft.com, faure@kde.org
http://perso.mandrakesoft.com/~david/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today