All other things being equal, you should get a "click" event for the first click and a "dbkclick" event for the second one.
There's not much that can be done about that. One problem is that most mouse drivers have the ability to allow the speed of double clicks to be configured to be quite slow. My mouse driver goes as slow as about 1 second. The driver can't know that the user is not going to click a second time until that second has expired. It would be unacceptable for the driver to wait for the absence of the second click before returning the single "click" event. Unless you've got a time machine that can look ahead to see if the user is going to click a second time, all you can do is delay your response to the "click". -- Mike Williams http://econym.org.uk/gmap --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
