Right. Ed, Ian's point was my point. If it panel is not visible, there is way for the browser to generate events for it. Even mouse move events, etc. GWT does not put listeners aside, but they don't cause extra overhead and occupy a negligible amount of memory. Basically, you don't have to worry about them. But if you will indeed "re-display" a panel at some point, it probably make sense just to hide it in the DeckPanel and pop it back to the top when needed. Of course, you always have the option of destroying panels in the deck if you feel that memory consumption becomes an issue.
-Brett On Jul 6, 6:15 pm, Ian Bambury <ianbamb...@gmail.com> wrote: > What listeners are you concerned about? You can't click something that isn't > visible. > Ian > > http://examples.roughian.com > > 2009/7/6 Ed <post2edb...@hotmail.com> > > > > > > > He Brett, > > > Thanks for your reply. > > Let me check if I understand you correctly: > > So if I remove a panel from the display (replacing A with B in the > > DeckPanel), the listeners of automatically deactivated. And they > > become active again when putting it on the screen again (replacing B > > with A in the DeckPanel)? > > > So the listeners are automatically put aside by GWT and don't cause > > extra overhead? > > > 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 Google-Web-Toolkit@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 -~----------~----~----~----~------~----~------~--~---
