With respect Rossko, I think you're missing the point. It's not me that's responsible for the hand changing to a finger pointer once the polygons are made clickable, that is something that's happening inside the google js script. If the polygons are unclickable and the mouse does not change to a pointing finger on mouseover then that HAS to be the state that the system returns to as soon as clickable is set to "false" again. You can see in my original post that I remover the listener, this post is about why the mouse still changes to a pointer when the listener is gone AND the "clickable" option has been set to false.
On Jun 20, 2:54 pm, Rossko <[email protected]> wrote: > > That's odd, as on my example it doesn't fire the click event as far as > > I can tell (until I set clickable true) so I wonder why on yours it > > still triggers the event? > > The 'click' event is one thing, setting up an event listener is > another. > There is nothing to stop one setting up listeners for events that > "should never happen" e.g. William's poly-click listener. > > You specifically make your own code remove the listener ; the event > could still happen but there is nothing to indicate that it has. -- 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.
