kconfig and kde global config files

Clarence Dang dang at kde.org
Sat Mar 4 10:31:00 GMT 2006

On Saturday 04 March 2006 14:36, Aaron J. Seigo wrote:
> reworking kconfig

Since you're working on KConfig :), I just wanted to mention this:

With KConfig being per application instance, having multiple instances of an 
application open results in a mess:

If one of these instances changes a config entry, the config change is not 
propagated to other open instances of the application even after 
KConfig::sync() e.g. the "Open Recent" menu in KOffice.

At least with the KDE3 API, the only way to get "propagation" working is to 
KConfig::reparseConfiguration() before every config read.  This is rather 
slow (200ms on my computer).

AFAIK, kdeprint uses a DCOP signaling mechanism to get around this problem but 
this should really be fixed at a KConfig-level since multiple instances of 
apps is quite common.


More information about the kde-core-devel mailing list