kconfig_compiler problem: no signals on changes

Richard Smith kde at metafoo.co.uk
Fri Mar 12 03:23:31 GMT 2004

On Friday 12 March 2004 2:13 am, Benjamin Meyer wrote:
> On Thursday 11 March 2004 4:23 pm, Waldo Bastian wrote:
> > On Thu March 11 2004 20:17, Richard Smith wrote:
> > > I was working on porting Kopete to use kconfig_compiler, and I hit a
> > > problem: there appears to be no way to make the generated configuration
> > > class emit signals when certain data members are changed. Have I missed
> > > something, or is it genuinely not possible to make the generated
> > > configuration object emit a signal when the configuration changes?
> >
> > That's indeed not supported at the moment, but I agree that it would be a
> > nice (optional) feature. I will add something like that in a month or
> > two, or if someone else feels like it they could have a go at it before
> > then.
> Guess till someone implements it, you could just delay porting from
> KAutoConfig.

Our 0.9 release (shipping with KDE 3.3) is going to be backwards-compatible 
with KDE 3.2, so this pretty much means we either delay porting until after 
3.3, or ship 0.9 with a copy of KDE3.3's kconfig_compiler. Neither sounds 
great, but the world ain't perfect...


More information about the kde-core-devel mailing list