Marcelo wrote: > Draggable polygons: > http://maps.forum.nu/gm_place_that_state.html > > or simply: > http://maps.forum.nu/gm_sensitive_circle2.html >
I read about your implementation and you seem to use some other map and you attach the polygons to that invisible map which makes the polygons move (grag around the real visible map). I'm using different approach: I handle drag, inside drag I calculate offset of lat and lon from original location and then recreate the new polygon in the new location. deleteVertex/insertVertex is TOO SLOW so it's not an option. The problem with my approach is that if I remove overlay and recreate a new one I loose all event handlers that I attached to the original polygon. Probably with your approach it works differently and this problem would be solved. However, original reason I posted was performance. The way polygons implemented I'm sure there has to be not performance penalty to drag them (if google gave offsetBy method to their GPolygon/GPolyline classes). In my implementation and yours if I drag around polygon I see 100% cpu load taken by the browser. I really don't care about that 100% cpu problem, but to me it means that something should be done differently/properly. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
