Chris, I looked through your code and couldn't find anything that would cause that behavior. It was a bit difficult to look through since it's distributed across multiple files and seems to have alternate loading techniques (e.g. ClusterMarker), so it wasn't clear where things could go awry. If you can cut your code down to a minimal example or use your expertise of your code to narrow it down further, we can take another look.
The only known bug that was introduced before 2.140 and is still unfixed is the iframe addOverlay issue, so I can't relate your map's behavior to any known issues. Apologies if you didn't receive the notice about the 2.140 upgrade. We posted it in the notify group ( http://groups.google.com/group/google-maps-api-notify) but I know there are still many developers that aren't subscribed to it, since we introduced it only last year. These upgrades will likely only happen once a year going forward. - pamela On Mon, Jul 13, 2009 at 6:35 AM, spunkmeyer <[email protected]>wrote: > > Oops - I was playing around with versions to see if something would > work and accidentally left it at 2.164. I originally had it at 2.s, > and have now changed it back. > > - Chris > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
