Thanks for the link. I already had found that though. The threads I could
find from that do say that HandlerManager will be undeprecated, but they
convey it in a way that implies that they wish it wasn't necessary. I am
left with the impression that there is a drive to get rid of
Excuse me for coming in late to the whole HandlerManager deprecation
business, but I just found out about it because I upgraded GWT and got
deluged with deprecation warnings, but...
What exactly is the problem with HandlerManager? I've seen some references
in old threads to its complexity.
http://groups.google.com/group/google-web-toolkit-contributors/browse_thread/thread/2e4c986ae1bd2c8b/551c19bbff3ed942
On Feb 14, 3:43 pm, malcolm.davis malcolm.da...@bms.com wrote:
Excuse me for coming in late to the whole HandlerManager deprecation
business, but I just found out about it
Hi everybody,
This is my scenario. My app is designed using Tabs concepts. Sometimes
the Tab 1 wanna be notified about something that happens on Tab 2-N.
For that, I have a singleton instance of HandlerManager. Now imagine
this: the user closed the tab 1. I think is a good idea keep my
Whenever you add an event handler to the SimpleEventBus (or even a
widget for that matter), it will return an instance of a
HandlerRegistration object. That object has only one purpose - to
remove the handler. Just hold onto those objects somewhere, and when
your tab gets closed, have them all
Oh, I didnt saw that. DUH!
lol
ty man
On Jan 10, 12:43 pm, Ben Imp benlee...@gmail.com wrote:
Whenever you add an event handler to the SimpleEventBus (or even a
widget for that matter), it will return an instance of a
HandlerRegistration object. That object has only one purpose - to
remove
You could also use a ResettableEventBus for each tab and then call its
reset() method to remove in one go all handlers registered through this bus.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to
