Wasn't it utvara who wrote: > >Hi Mike, > >There is a flaw in your advice :) or to be more precise the way you >are suggesting is: > >1. create overlay >2. let user click randomly on the map >3. analyse that click server side and return response
I wasn't saying that's how Google do it. I'm just saying that you can get something that works that way, just without the hotspot cursor change. I wasn't keen on going through all the bother of deciphering the system that the Google API uses to process the hotspot list that it gets back from the server just to satisfy someone's curiosity. The API code isn't easy to decipher. The API makes a call to the server to obtain a list of hotspots. It then monitors "mousemove" events and performs a quadtree search to see if the mouse is over a hotspot. When there are many hot spots on the map, a linear search would be likely to be too slow. The API quadtree code isn't exposed, so if you wanted to do the same thing yourself, and had enough hotspots that a linear search wasn't fast enough, then you'd have to have your own quadtree code. It looks like you're just as capable as I am at working out how Google do it. >BTW I'm new around here and I'm not sure if reverse engineering Google >data/js is legal at all. No it's not. See 10.5 in the Terms. -- 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 -~----------~----~----~----~------~----~------~--~---
