[PATCH] Add signals support to kconfig_compiler

[Michaël Larouche]

Le Vendredi 3 Février 2006 08:59, Michaël Larouche a écrit :
> Le Jeudi 2 Février 2006 05:34, Cornelius Schumacher a écrit :
> > On Thursday 02 February 2006 02:24, Michaël Larouche wrote:
> > > I define signals to get a flexibity. Maybe multiple entries would want
> > > to emit the same signal. And that same signal would maybe need to pass
> > > more than one argument.
> >
> > Why would the signal have to pass arguments at all? They could just as
> > well be fetched from the config object.
>
> True. But it can be good IMO to allow passing arguments to the signals.
>
> Ex. I have a slot that take a path as a argument. It is used in several
> places.
> void setStylePath(const QString &)
>
> If my configuration class can pass arguments to these signals, I can reuse
> the same slot that others classes use too.
>
> In other news, I'll add the generic signal today when settings has changed.

I finally added the signal to KConfigSkeleton class, so users of 
KConfigSkeleton that doesn't use KConfigXT will be able to react to config 
changes anyway.

See the new updated version attached.
-- 
Michaël Larouche (Shock The Dark Mage)
KDE developer working on Kopete, Kamefu...on dial-up :P
--------------------------------------
Blog: http://mlarouche.blogspot.com/
MSN/Email: michael.larouche at kdemail.net
IRC: irc.freenode.org/DarkShock on #kopete,#solid,#kamefu,#plasma
Jabber: darkshock at myjabber.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: kconfig_signalsupport_v2.patch.gz
Type: application/x-gzip
Size: 9455 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060203/ac89ead7/attachment.bin>