> > Instead, just hide() the GScreenOverlay. > > Bother! It seems that clearOverlays(); also triggers the errors. I > was planning to use this function elsewhere on my page. > > Maybe I'll just suppress the script errors - which would also be an > unsatisfactory solution.
I'm presuming you'll be going on to do other things with this map later. I have a feeling that anything you do with overlays of any kind is going to trigger the error after resize, so you're going to have to fix it. I'm pretty sure I was looking at versions that broke in the checkResize, removeOverlay and addOverlay, depending what was done first. Feeling in the water that they all do the check- resizing activity within the API maybe? I think Bruce is on a clue. Maybe the browser implements div size changes slowly - after all, it has to re-render the whole page twice as the height and width changes - and you should be looking to delay ANY API functions - the GScreenPoint calculations - until the browser has settled down. That other marker-based example is triggering off the APIs own map resize event, which has got to be further along the chain. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
