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

List:       kde-devel
Subject:    Re: shared kconfig?
From:       Stefan Kombrink <katakombi () gmail ! com>
Date:       2006-01-23 12:42:08
Message-ID: 3f6a1ade0601230442i7fd66868r4152a54cb27a6bb7 () mail ! gmail ! com
[Download RAW message or body]

thanks for your suggestions, the ladder seems to be the solely
solution indeed :)

On 1/23/06, Lubos Lunak <l.lunak@suse.cz> wrote:
> On Monday 23 January 2006 12:00, Adriaan de Groot wrote:
> > On Mon, 23 Jan 2006, R.F. Pels wrote:
> > > On Sunday 22 January 2006 23.38, Stefan Kombrink wrote:
> > >> I want to share the same kconfig file with two different applications.
> > >> Is that possible?
> > >
> > > Why not?
> >
> > Implicit in the question: "without destroying the integrity of the file".
> > Yes, multiple applications can open the same KConfig file. If only one of
> > the applications writes to the file, then a simple setup with a dirwatch
> > and read-only access in the remaining applications will do. If you have
> > multiple applications writing to a single config file, you will need to
> > coordinate things.
> >
> > >> I couldn't find something like a signal that is emitted when the
> > >> configuration on disc (in the rc file) changes?
> > >
> > > Have a look at KDirWatch.
>
>  The usual technique in KDE is to use a DCOP call to re-read the
> configuration
> in the other app.
>
> >
> > There's also KSharedConfig which might do the job.
>
>  No, KSharedConfig is basically just a KConfig with a reference count.
>
> --
> Lubos Lunak
> KDE developer
> ---------------------------------------------------------------------
> SuSE CR, s.r.o.  e-mail: l.lunak@suse.cz , l.lunak@kde.org
> Drahobejlova 27  tel: +420 2 9654 2373
> 190 00 Praha 9   fax: +420 2 9654 2374
> Czech Republic   http://www.suse.cz/
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe
> <<
>
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]