> Initial development was carried out using version 2.149. I wanted to > use a polyline as a cursor to mark the clicked position, but for some > reason the polyline would not display. Using the same code but > replacing the GPolyline command with GPolygon works fine: > > http://rrc22a.vet.cam.ac.uk/maptest/region.cgi?gmapv=2.149 > (click on the image to display the cursor). > > There appears to be a change in versions 2.150+, as in the newer > versions the cursor does not appear regardless of whether I use a > polyline or polygon.http://rrc22a.vet.cam.ac.uk/maptest/region.cgi?gmapv=2.150
Guesswork : The polygon in the fix has only two vertices. Later API versions may not like that. So let's figure out why the polyline version didn't work , as that would be the "correct" way. In Mercator projection, latitudes 90 and -90 are to be avoided or they'll blow up any calculations with infinite numbers. Even though you've constructed a Euclidean space the API may still be protecting itself ... I'd try your cursor as a polyline from -80 to 80 just as a guess? Innovative use of API there !! cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
