> You're breaking the principle of least surprise: if I register a > handler on a widget, I expect the source of the event to be that
Exactly my point why I want to change the source. Your suggestion works with single widget components, but not really wel for composite widgets. Example: suppose you have a composite widget that contains a chexkbox and label. The composite contains a addClickHandler method to add a click handler. This method will simple forward the call to the underlying checkbox and label. The listener will expect the source to be the composite widget like you mentioned above, which isn't the case in the above (in the past you could change the sender widget in the listener). Note: ofcourse you can create a single listener in the composite that is added to the checkbox and label that will forward his event to the contained listeners. But don't forget this is just an example and there are more where this is desirable.. -- Ed --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
