Yes, this API is thoroughly broken and you are the first to notice it. It's written like gibberish because it's not open source. If you'd like to contribute to an open-source mapping API see http://wiki.openstreetmap.org/wiki/API
> but it's broken and I'm not sure if it's my fault or it's gmaps fault. To see > why it's broken, try to drag around a marker like a madman on the second > page, the problem will be obvious. Same problem happens with IE. I didn't > test it with Chrome though. The thing is that initially I was working on a > quad core pc and this problem never happened... That's probably due to reentrancy of the redraw code. It can be quite difficult to work this stuff out, gave me a headache when I tried years ago. I can point you to a custom overlay that used to exhibit a similar problem but got fixed - http://www.bdcc.co.uk/Gmaps/BdccGmapBits.htm the Graticule code - but as you say, you're not interested. A quick detection is to implement a global counter in the redraw code ; increment on entry, decrement on exit, alarm on value > 1 > But, after I tried to do it I was surprised that there is no clear way to do > simple stuff and it all seems to be broken behind the scenes. Perhaps you are overcomplicating the approach, if you have experience elsewhere. Few API users mess with custom overlays to draw a circle ; as you point out, GPolygon is perfectly capable of handling this itself and just needs to be supplied with an array of points. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
