From: SourceForge.net <no...@so...> - 2011-11-29 03:54:00
|
Bugs item #3444764, was opened at 2011-11-28 19:53 Message generated for change (Tracker Item Submitted) made by twelvechairs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=470969&aid=3444764&group_id=53614 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: 12 chairs (twelvechairs) Assigned to: Nobody/Anonymous (nobody) Summary: not all signal connections being performed... Initial Comment: button.signal_connect("enter-notify-event") {print "hello "} button.signal_connect("enter-notify-event") {print "world\n"} The above does what I expect it to do (ie. when I scroll over the button it prints "Hello World" ) button.signal_connect("enter-notify-event") { print "Hello ";[]} button.signal_connect("enter-notify-event") { print "World\n";[]} However this code will not perform the second event (nor any subsequent) - When I scroll over the button it prints "Hello " only (not "World\n"). This seems to be because ending the proc performed by the signal in an Array will somehow stop the second signal_connect from performing its associated Proc. Using Ruby 1.8.6 and ruby-gnome2-0.16.0-1-i386-mswin32.exe (2007-02-12) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=470969&aid=3444764&group_id=53614 |