Thank you, Jeff, for posting that to the group. On Fri, Sep 4, 2009 at 1:39 AM, Jeff dePascale<[email protected]> wrote: > > In case anyone ever runs into this issue, I figured out where the > error occurs. Casting the loaders content to a DisplayObject (or > anything that extends it) allows you to utilize the loaders content > outside the context of the loader itself, which then allows you to > reuse that loader object, shaving some overhead and assisting in > garbage collection if you manage those children properly. A common > practice, but it fails here because the loader.unload() method (which > will reset the properties of the loader to a null state for next load, > clearing the content property in the process) was firing directly > after the load, not prior to the next load. Normally not an issue > since you've already referenced the child content for use elswehere, > so it lives on despite the loader resetting. The problem is that an > Event.UNLOAD is still dispatched to that child when the unload method > is called. I am assuming there is something listening to Event.UNLOAD > since the 1.5 release of the maps API. Moving that unload call to > (where it should be anyway) the next load solves the issue. However, > it is worth noting that this means that using the same loader object > for multiple, simultaneously loaded objects will result in > event.UNLOAD events being dispatched to all of those children if unload > () is ever called. Fixed now on my end... > > >
--~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API For Flash" 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-maps-api-for-flash?hl=en -~----------~----~----~----~------~----~------~--~---
