I think I may have found a bug, but it's hard to isolate (it's in the middle of a complex app), so I want to get some feedback before I write it up properly.
The problem occurs when I have two or more polygons, exactly one of which is editable at a time. To change to editing another polygon, you click on it, and enableEditing() is called for it (and disableEditing () is called for the others), and the map is centred on the "new" polygon. Here's how I get the bug: I have two 4-point polygons, A and B. I delete a point from A (thus turning it into a triangle). Then I click on B. Editing is enabled, but when the map is centred, the last vertex of B (and the mid-line "ghost point" which precedes it) does not follow the rest of B. Even more strikingly, clearOverlays() does not always remove these "zombie points". That is, I put an alert() immediately after my call to clearOverlays(), and in some cases, those two points (one with a solid border, one "ghost") are still there. To me that indicates that it's probably not my code at fault. Thanks for any ideas! Nick --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
