:: It sets the signal return value to the value returned by the last :: handler. It then decides whether to continue the emission if theBecause the default handler for button_press_event on GtkCList claims to have handled button-1 events, but not button-2 or button-3 events.
return :: value is False.
:: >>Most uses of stop_emit_by_name() can be converted to simply do
"return :: >>True" now. You hardly ever need to manually stop the emission for
:: event :: >>signals in GTK 2.x.
But, if the default handler do so, why I can have a
w.connect_after('button_press_event', cb ) and the signal is triggered
for middle and right button pressed signals an not for the left button
pressed signal (tested with a clist)?
Really? Can't you just use connect() and return True when a double click is performed (event.type == gtk.gdk._2BUTTON_PRESS)?
:: >Why did we have to do it back in GTK 1.2? :: > :: Because 1.2 didn't use the above accumulator. Hm, seems to me that some logic have to change if code is ported from
1.2 to 2.0. This makes the event propagation very hard to design. If I
want an action on a double-click at a (clist)row I have to do a lot of
extra work in 2.0. There are some other solutions?
James.
-- Email: [EMAIL PROTECTED] WWW: http://www.daa.com.au/~james/
_______________________________________________ pygtk mailing list [EMAIL PROTECTED] http://www.daa.com.au/mailman/listinfo/pygtk Read the PyGTK FAQ: http://www.async.com.br/faq/pygtk/
