On 12/20/10 11:05 AM, Ed Leafe wrote: > On Dec 20, 2010, at 1:47 PM, Paul McNett wrote: > >>> Both are bound. You can have multiple handlers for a given event. Try >>> adding some debug output to those two handlers to see that they are both >>> called. A common case is for some behavior to be bound at the framework >>> level, and then have the developer bind additional behavior at the >>> application level. >> >> If the first handler calls evt.stop(), the second handler won't get called. > > > Actually, if the *second* handler that is bound calls evt.stop(), the > first one bound won't get called. Events get handled in the reverse order of > their bindings. Try running this sample code:
Right, that's what I meant. The first handler called is the last handler bound. If any handler in the chain calls evt.stop(), it'll keep the rest of the handlers from getting a whack at the event. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
