[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KConfig::addConfigSources is broken
From:       "Thomas Braxton" <kde.braxton () gmail ! com>
Date:       2007-11-18 18:08:59
Message-ID: 928c3f1b0711181008v32ccfcffx4831a0394b31fdef () mail ! gmail ! com
[Download RAW message or body]

On 11/18/07, Andreas Pakulat <apaku@gmx.de> wrote:
> On 18.11.07 11:30:33, Thomas Braxton wrote:
> > On 11/18/07, Andreas Pakulat <apaku@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".
>
so the name passed to KConfig doesn't matter, the last file passed in
is considered to be the most specific file?
[prev in list] [next in list] [prev in thread] [next in thread]