On Dec 2, 4:44 pm, John Mick <[email protected]> wrote:
> Ah I missed the MVCObject/MVCArray section in the API - I'm going to
> work on putting together a sample application today to test this
> approach and I'll be back with my findings soon. Thank you for this
> tip. :)
The "setPath" / "setPaths" methods also accept standard JavaScript
arrays. Unless you are planning to do interactive editing of your
polys, I can see no reason to use MVC arrays. It is just extra
overhead to frustrate the garbage collector. A total rebuild of your
polys is less likely to cause leaks.
I might have an alternative to using API polys:
http://www.polylib.us
but I cannot link to your application to test it first. I am looking
for a clickable link, not raw code.
--
You received this message because you are subscribed to the Google Groups
"Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
