Well, about the API version, I was under the impression that the API will still be supported for a fair amount of time to come to give us enough time to port our website to the newer version. We are in the midst of deploying a bunch of stuff and this porting is not the highest priority. Since you pointed it out, would you also be able to give me some advise (or a link to information) on the best way to manage the port to newer API? I don't think we want to necessarily make the jump to V3 just yet, but I'm sure we would gladly go to a more current version of V2 if we can without fighting too many fires. Thanks.
Some information that I didn't provide in my original post, we are using kml files generated using Google Earth to display the route traces. The kml files are all fine (else they wouldn't work in Chrome and FF, right?). Also, I would really like it if someone could tell me as to how exactly does one use an event handler for the load() event on the GGeoXml object. Thanks, kaymo On Feb 7, 11:56 am, ProbablyMike <[email protected]> wrote: > Hi, > > Tried it a quite a few times in IE8 and it seemed to work okay, the > points & route changed every time, maybey just lucky. > > "If it helps to know, we are using version 2.136 of the maps API." > Oh no you're not!!! The oldest version of the API now available is > 2.285http://groups.google.com/group/google-maps-api/browse_frm/thread/cba4... -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
