Thanks for bringing this up to our attention Yanko. I couldn't replicate the bug in the first example. The second one, I did. I'll patch up these examples with a fix by next week. I'll also revisit the use of 'pathCoordinates' and may simply remove it from the example as it does seem confusing the way it's being used.
Thanks, Dann On Feb 12, 11:46 am, Yanko Hernández <[email protected]> wrote: > On Feb 8, 1:49 pm, Daniel Lee <[email protected]> wrote: > > > We've recently pushed out a new version of the API. > > ... > > Please test and provide feedback. > > (1)http://code.google.com/apis/maps/documentation/v3/examples/polygon-ar... > > fails on these lines: > > (55) contentString += "Clicked Location: <br />" + event.latLng.lat() > + "," + event.latLng.lng() + "<br />"; > > (65) infowindow.setPosition(event.latLng); > > Firefox reports "event.latLng is undefined". It appears there is some > kind of mangling related with the ids generated by the javascript > optimizer, because "event" only contains a field named "Hk" (found it > by placing a break point in the offending line). > > (2)http://code.google.com/apis/maps/documentation/v3/examples/polyline-c... > > works, but not as intended > > pathCoordinates.length is always 0, so every marker's title will be > "#0" and every marker inserted will be at the head of the list/array. > > Replacing "pathCoordinates.length" by "path.length" works as intended. > But I don't understand this example 100%: What was the intended use of > pathCoordinates? To hold a reference to the list/array of "latLng"s? > > Greetings > Yanko -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
