Look at www.marsrutai.info/directions.htm#-24.86775,113.66916,-31.87809,115.83885,-27.44842,153.01783
It iterates through all segments of route and still works much faster than your solution. Also fast in IE7. The finding of closest point is in function getProximity(mouseLatLng) The approach was to convert and store polyline vertices coordinates in pixels after each zoomend event. Then calculating closest point is simple and fast math operations, even every route segment is visited. Evaldas On Jun 26, 12:33 pm, epicycler <[email protected]> wrote: > demo at > > http://www.epicycles.com/demo/simple.php > > best in FF, IE6/7 slow, IE8 workable, untested elsewhere --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
