Thanks again for the suggestions. In response to Ross K's comments, i think that the different behavior is because the sequence is:
on first load, removeOverlay() is not called (because the overlay is null) on the second load, removeOverlay() is called (after the resize) and then a new overlay is added on the third resize, changing the div size throws the errors. If the removeOverlay line is ommitted, there are no errors. So something in removeOverlay then causes the resizing of the div to break. My hunch is that this may be something specific to GScreenOverlays, but this isn't tested yet. In the post recommended by Bruce this page is given as an example: http://googlemapsapi.martinpearman.co.uk/infusions/google_maps_api/basic_page.php?map_id=6 Interestingly, it doesn't use GScreenOverlay, but uses a standard marker that is moved back to the screen center when the map moves, to acheive the same result. I will have a play with using the resize event and also using a standard marker, and post back the results. Thanks, Will --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
