Urgh. Sorry...never should have mentioned "listeners". (Old habits die hard. )
I *should* have written, "it seems like you may still need to manually remove handlers of "logical" events". jay On Jul 19, 4:32 pm, jay <jay.gin...@gmail.com> wrote: > Ah, so that's good for handlers of *DOM* events [e.g., using > addDomHandler()]. For "logical" events [those added via addHandler()], > however, it seems like you may still need to manuallyremove > listeners. > > Is that correct? > > thanks! > > jay > > On Jul 19, 3:23 pm, Thomas Broyer <t.bro...@gmail.com> wrote: > > > > > On 19 juil, 23:15, jay <jay.gin...@gmail.com> wrote: > > > > Where do you see the automatic removal of handlers? There's nothing > > > when a widget is unloaded, and I can't find anything that would do any > > > cleanup. Maybe there's some code somewhere to do cleanup as the app > > > is shutting down? > > > onDetach calls setEventListener(getElement(), null) which is enough to > > mitigate memory > > leaks:http://code.google.com/p/google-web-toolkit/wiki/DomEventsAndMemoryLeaks > > And on "window.onunload", all RootPanels and wrap()ed widgets are > > detached, so their onDetach method is called (which recursively detach > > their children). -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
