KConfig::addConfigSources is broken

Andreas Pakulat apaku at gmx.de
Sun Nov 18 17:50:27 GMT 2007


On 18.11.07 11:30:33, Thomas Braxton wrote:
> On 11/18/07, Andreas Pakulat <apaku at gmx.de> wrote:
> > Hi,
> >
> > seems like KConfig::addConfigSources is broken, wrt. writing to the
> > configuration.
> >
> > When creating a KSharedConfig instance with:
> >
> > d->m_cfg = KSharedConfig::openConfig( d->projectTempFile );
> > d->m_cfg->addConfigSources( QStringList() << d->developerTempFile );
> try changing it to
> d->m_cfg = KSharedConfig::openConfig( d->developerTempFile );
> d->m_cfg = addConfigSources( QStringList() << d->projectTempFile );
> since the developer file is imho the most specific file, the file name
> passed to KConfig is considered the most specific file.

Thats

a) the opposite of what the API docs say
b) a behavioural change thats undocumented

So either fix the api docs and add mentioning of this to
KDE4PORTING.html or revert to the old behaviour of "last in, first out".

Andreas

-- 
A day for firm decisions!!!!!  Or is it?




More information about the kde-core-devel mailing list