On Oct 7, 5:51 am, ang <[EMAIL PROTECTED]> wrote: > Thank you very much Rossko. > > I've changed to v=2.100, now it works good like it used to.
You may want to track down the error so it works with v2, at some point v=2.100 may go away (hopefully when there aren't any regression problems). See this thread: http://groups.google.com/group/Google-Maps-API/browse_frm/thread/b9d64a48638b2fc3# -- Larry > > Thanks. > > On Oct 6, 7:05 pm, Rossko <[EMAIL PROTECTED]> wrote: > > > > i didn't change the version number. always it has been v 2.x i've > > > created the map like this year March. > > > Understand that v 2.x is not a specific version - it means "get me the > > latest development version", which gets updated just about every week! > > > Recent changes include modularisation of some parst ofteh API code - > > taking soem parst out of the main API script and loading them when > > needed. This does upset some maps with time-critical parts. > > > Anyway, you can specify and older, fixed version number like v=2.100 > > to try it. > > > cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
