[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-19 5:19:36
Message-ID: 928c3f1b0711182119m6ce375cctbb5771eb4cb80aa8 () mail ! gmail ! com
[Download RAW message or body]

On 11/18/07, Aaron J. Seigo <aseigo@kde.org> wrote:
> On Sunday 18 November 2007, Thomas Braxton wrote:
> > I tested this, and the symmetry is still there. Try my previous
> > suggestion and if it still doesn't work, then we have a bug, which
> > I'll gladly fix. I don't see how opening one file, then expecting
> > writes to go to a different file is symmetrical, or sensible. But, if
> > that's the way you want it I can easily change it.
>
> so are you saying that with these files:
>
> projectTempFile:
> [Project]
> Name=Foo
> VcsPlugin=Bar
>
> developerTempFile:
> [Project]
> VcsPlugin=Foobar
>
> this:
>
> d->m_cfg = KSharedConfig::openConfig( d->developerTempFile );
> d->m_cfg = addConfigSources( QStringList() << d->projectTempFile );
>
> will get you this on reads:
>
> VcsPlugin => Foobar (NOT Bar)
> Name => Foo
>
> and when Name is set to Bar it will write that value out to
> d->developerTempFile?
>
yes :)
[prev in list] [next in list] [prev in thread] [next in thread]