On Oct 2, 8:47 am, simonrl <[EMAIL PROTECTED]> wrote: > On Oct 2, 12:38 pm, Mike Williams <[EMAIL PROTECTED]> wrote: > > > That's really useful, because all the previous pages that have reported > > that problem have had huge quantities of other stuff going on at the > > same time, so it's been hard to tell what's really going on. > > snip > > > One thing that's become apparent is that the problem only occurs in > > v2.129a onwards, so you can get round it by using &v=2.128d instead > > of &v=2 when you load the API code. > > Thanks Mike (and Mike in Stroud), specifying 2.128d did indeed fix the > issue. Really appreciate the feedback. Have starred those topics. > > Apologies for posting that unreadable untabbed code - didn't know if > it was etiquete or not to post code or just a link ;)
As a matter of curiousity, did you see the sticky post at the top of the group, the one with the title: BEFORE YOU POST: Read our Suggested Posting Guidelines! That links to this: http://groups.google.com/group/Google-Maps-API/web/suggested-posting-guidelines -- Larry --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
