On Aug 28, 9:50 pm, Thomas Broyer <[email protected]> wrote: > > > I have a button with three click handlers registered. They are > > chained so that the calling order is A, B, C. > > IMO you shouldn't depend on your handlers call order, you'd rather > have a single handler that eventually defers to "subhandlers" (that'd > probably wouldn't be ClickHandler's actually) to enforce the call > order and what to do on each step. > > > Is it possible in handler B to "cancel" theeventso that further > > handlers are not called? > > No. Actually I think this would be useful as well. If we were only supposed to use one click handler then there'd be setClickHandler, not addClickHandler. Cancelling event propagation is possible (parent handlers), so why shouldn't we apply this to sibling handlers as well? If you're using MVP and you put the validation rules in the view, but the processing in the presenter then you can't use a single click handler with sub-handlers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
