On Mon, 2007-12-17 at 11:06 +0000, Matthew Allum wrote: > > > Input events are handled initially by the stage the event will enter a > > > capture phase continue down through children to the 'source' actor of > > > the event (for example the actor that was clicked on) before then > > > entering the 'bubble' phase going back up through parents to the > > > stage. > > > > Does this really meant that the stage gets two chances to handle an > > event? > > Yes. It is like the W3 event model.
just to clarify: every actor will have two chances to handle an event, but using *two* different signal handlers. the handler attached to the ::event signal will be called in bubble phase, the handler attached to the ::captured-event signal will be called in the capture phase. you can think of the event handling as the same as the GTK+ event handling model (bottom to top-level), plus a preliminary phase running in the opposite direction (top-level to bottom). an event can be received in both phases, or blocked in either one. > > > The event can be stopped at any stage by an actor in the event > > > pipeline. > > > > By the way, this "return true to stop further signal handling" really > > should be in the API reference for each signal. > > > > Agreed - Ebassi ? as I replied already, it's written in the notes on the event handling as well. we can write it for every signal, but it would be kind of repetitive. ciao, Emmanuele. -- Emmanuele Bassi, OpenedHand Ltd. Unit R, Homesdale Business Centre 216-218 Homesdale Rd., Bromley - BR12QZ http://www.o-hand.com -- To unsubscribe send a mail to [EMAIL PROTECTED]
