On May 3, 10:47 am, denis56 <[email protected]> wrote: > Still do not understand why > would parent element first remove reference to the instance before > putting it at a different location?
I'm pretty sure it's to ensure that code written with GWT doesn't leak memory. If you let the original parent keep the reference to the widget once it has been adopted by another widget, how can you ensure that once that widget isn't displayed anymore, nobody references it ? If there are any references left in the code, the widget won't be garbage collected. If you want to know more about the strategies adopted by GWT to prevent memory leaks, I recommend reading this excellent article in the wiki: http://code.google.com/p/google-web-toolkit/wiki/DomEventsAndMemoryLeaks and all of the related links. Cheers, Salvador --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
