Just to chime in here - I have been using the same approach as
suggested earlier to ensure that you get the latlng of the point
clicked on a map, even if there is an overlay 'in the way', and it has
worked well for me for quite a while.
In my case, I'm plotting points, polylines and polygon features from a
SQL Server 2008 database within a 50km of the area clicked, and
sometimes the features themselves are quite large which means that the
coordinates were being passed to the click handler in the
overlaylatlng rather than in latlng. Using the following:
function mapClick(overlay, latlng, overlaylatlng) {
if (overlay) { latlng = overlatlng }
Means that latlng will contain the latlng of the clicked point on the
basemap, even if there was an overlay in the way...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
