> about the second comment, I'm sorry but i don't understand, you're > saying that the V3 API 'promotes' the json objects to be JS objects? > what for? why not keep it as json and if need be, the js developers > can 'promote' it on their own.
Because almost every use for this requires an actual JS object. Why force the majority of developers to create a LatLng object? I believe your root issue is that the LatLng object serializes to something you can't use. Instead of using JSON.stringify, why not create your own function to walk through the returned data and create a proper JSON string. The function wouldn't even be that complex. Chad Killingsworth -- 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.
