Thanks for the tip Thomas, sure is usefull. Yep, I know about the sinking, but I already toke care of this myself in a lazy fashion. I extend all the basic objects like TextBox and Label and override all the add**Handler().. which are forwarded to a Observer instance that contains my own version of the HandlerManager (I just rewrote it all : ( )... Why ? Because I can't inject my own HandlerManager and I need things like an interceptor in the HandlerManager, and some more small checks..
Tanx -- Ed On May 5, 3:40 pm, Thomas Broyer <[email protected]> wrote: > On 5 mai, 08:30, Ed <[email protected]> wrote: > > > And another thing: > > > How do I change the source object that is contained in the event (like > > using a proxy object)? > > This one's easy, so I'll answer; I'll let the GWT team answer you > other concerns ;-) > > > I mean: the source object is determined when the HandleManager is > > created and can't be changed anymore. > > In my current gwt 1.5 code I changed this source such that it matched > > the expectations of the user receiving the event. > > Now, this isn't possible anymore... > > Use Widget::fireEvent(GwtEvent<?>), it'll "re-fire" an event with the > source adjusted to be the widget used. > > You can also use Widget::delegateEvent(Widget,GwtEvent<?>) which just > calls fireEvent on the target Widget. > > > Hmmmm, what are the advantages of the new event model? > > It doesn't sink events that you're not interested in (think > KeyboardListener and MouseListener), which makes your app a bit more > reactive. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
