I reported a similar bug but was told it could not be duplicated thus
no action to fix it. "It must be just my machine". It appears it is
not just my machine. The "click" event listener introduced a timer to
measure the delay between clicks. Successive clicks without a large
enough interval are discarded. It breaks previously working
applications.
I found a "workaround". I added a real "onclick" event handler to the
map's container DIV. The actual arguments are obtained from the
"mousemove" event listener. It is actually faster than using the
API's "click" event listener because it does not have to crawl through
additional overlays.
Try:
www.polyarc.us/polybuilder
If it works for you with your device, please join me in asking Google
to fix the "click" event listener bug.
Sure, you can hard wire you application to v=2.121 but you cannot use
the thousands of other applications developed by others with your
device. You cannot use your device with maps.google.com unless Google
acknowledges the bug & corrects it.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
