On Oct 29, 4:04 am, mivemu <[EMAIL PROTECTED]> wrote: > > A possible solution would be google allow programmers post a tag 'API > = v1' or something into map code, so new commands , (to say V2) won't > apply to that source. > > Only when programmers want upgrade to new API with tag API=v2 new > commands would apply
Version 2 has been out for two and a half years, and version 1 was turned off a year ago. Specifying v=1 in the API script tag, which is what you are suggesting, did work until v1 was turned off. Using v=1 now gets you v=2. Although there were concessions made in v2 of the API so that v1 code would continue to work (up to a point) no-one should be using version 1 code any more. What doesn't help is that there are various books in print which do use version 1 syntax. Andrew --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
