kconfig and kde global config files

Tobias Koenig tokoe at kde.org
Mon Mar 6 22:41:36 GMT 2006

On Mon, Mar 06, 2006 at 01:29:38PM -0700, Aaron J. Seigo wrote:
> On Sunday 05 March 2006 23:18, Tobias Koenig wrote:
Hi Aaron,

> >  And why shouldn't it be possible to put the parsing code 
> >  into a separated thread?
> well, that doesn't make it faster (the contrary, actually), it would just keep 
> it from interfering with UI updates and other orthogonal tasks. of course, in 
> the case where it's parsing in another thread then things needing the new 
> config would have to wait for it to be done; this would add additional 
> complexity.
Hmm, but normally you don't access the config value in application B as
soon as application A has changed it. So when the dir watcher of
application B detects a change of the config file, its kconfig object
reparses the file in a separated thread in the background and when
application B will access the config value the next time, it's already
up to date.

We could also add the reparsing step between the dir watcher and the
application level signal for 'config changed', so application B gets the
signal after the config file has been reparsed.
Normally changing a config value isn't time critical for other
applications, so a delay of 1 second is ok as long as the GUI is not

Separate politics from religion and economy!
The Councile of the European Union is an undemocratic and illegal institution!


Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de

More information about the kde-core-devel mailing list