On Thu, 24 May 2001 [EMAIL PROTECTED] wrote:
> Well, this is straight forward in pygtk1.2:
> >>>hscale.get_adjustment().connect("value_changed",value_changed_fn)
> with something like:
> >>>def value_changed_fn(adjustment):
> Does pygtk2 do it differently?
Please note that you are _not_ in this case creating a new signal; just
setting a handler to an existing signal. This is _not_ what Skip has
requested, AFAICS. Skip, there must be something in the code, and IIRC
James did mention it a while back.
Take care,
--
/\/\ Christian Reis, Senior Engineer, Async Open Source, Brazil
~\/~ http://async.com.br/~kiko/ | [+55 16] 274 4311
_______________________________________________
pygtk mailing list [EMAIL PROTECTED]
http://www.daa.com.au/mailman/listinfo/pygtk
