Wow. Fast response. Thanks Mike. #1 worked fine. I'd be interested in #2, except I'm not quite sure how to execute it. In any regard, your tutorials are the best. Thanks much.
On Jan 18, 12:24 am, Mike Williams <[email protected]> wrote: > Method 1. If you use EGeoXml or GeoXml instead of GGeoXml you would be > able to add {polygonoptions{clickable:false}}, in which case all the > clicks drop through to the map. > > Method 2: Since you don't appear to be filling the polygon, you could > replace it with a polyline by using a KML <LineString> in which case > only clicks on the line would be intercepted. > > Method 3: You could listen for map "addoverlay" events, looking for one > that's an instanceof GPolygon, then make a copy of it with > {clickable:false} and remove the original one. [Be careful not to get > into a loop when you get the "addoverlay" event for your new GPolygon.] > > Method 4: You could listen for map "addoverlay" events, looking for one > that's an instanceof GPolygon, then add a "click" listener to that. Your > polygon "click" listener could either perform your user click processing > directly or trigger a map "click" event that would be picked up by your > existing map click listener. > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
