On Jun 10, 10:46 pm, Rossko <[email protected]> wrote: > > I do get a script error during map initialisation, associated with > fromPixelToLatLng, which suggests something to do with your custom > map. Couldn't say what, not familiar with those.
You're right; I do too, now. It looks like the API tries to do its calculations at zoom 19, so Mike's caveat >> Potential Pitfalls 1. Some API features, such as polylines and ground overlays, perform their calculations at zoom level 17, rather than at the max zoom level of the map type. These features will fail if the GProjection() of the map type ahs less than 18 zoom levels. << looks out of date. Try using new GMercatorProjection(20) in the code and see if that fixes it. > You are asking for v=2 but getting served 2.242c ; I'm sure that ought > to be 2.225 according to the changelog See this thread, which details the update strategy: http://groups.google.com/group/google-maps-api/browse_thread/thread/78991bdfc3760376 -- basically, update the code then get round to telling everyone, then do something about documenting it all. Maurizio may be the first casualty with the new v=2. -- 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.
