Ok, I think I have a solution for the moment - don't use removeOverlay ()!
Instead, just hide() the GScreenOverlay. This has the desired effect, and doesn't throw any errors. I'm not completely happy with it, as presumably somewhere in memory instances of the overlay will be stacking up - but I don't expect users to be resizing the screen too often so can probably get away with it. Using settimeout() with a slight delay (and cancelling if it is retriggered before the timeout has run) should mean that excessive instances of the overlay are not generated by browsers that continuously fire the resize event whilst the resize is in progress. Thanks for your help, any suggestions on a better solution still welcome! PS. tried making use of the map resize event, but this didn't make a difference. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" 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?hl=en -~----------~----~----~----~------~----~------~--~---
