The reason for the cycling method is simple. If the API had a method for every possible scenario, it would be 10 gig in size and impossible to load. We are left with the ability to manage it any way we want. If you want a group of markers to show/hide, then you do it. If it was done inside the API, that code would have to be executed in a very similar method, iterating through an array of markers. Since this code is left to the developer, other developers who don't want to show/hide markers by group don't have to suffer with that code bloat for that function. Doesn't this make sense?
-John Coryat http://maps.huge.info http://www.usnaviguide.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
