Thanks William! I should have thought of that :) On Jul 20, 7:47 pm, William <[email protected]> wrote: > On Jul 21, 2:18 am, helen <[email protected]> wrote:> or if I should be > doing something differently. > > it seems to me that the current version of the API is fixing problems > due to event propagation, where in previous versions a click on a poly > was also registered on the underlying map. So the current behavior is > to capture the event on the poly. > > http://code.google.com/p/gmaps-api-issues/issues/detail?id=2172 > > I remember this from a long time ago when developing a drag-zoom > control, where the second click is usually registered on the animated > poly instead of the underlying image (and you will see the cursor > change to pointer), so you will need something like this after you > create the polyline: > > var poly = new google.maps.Polyline({ > strokeColor:'#ff0000', > strokeOpacity: .8, > strokeWeight: 3, > path: [latlng]}); > > poly.setMap(map); > google.maps.event.addListener(poly, "click", function(me) { > addPolyline(me.latLng); > > }); > > ...
-- 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.
