Wasn't it blabyboy who wrote: >> I'd also suggest ditching MarkerManager, since it looks like you're >> actually duplicating its functionality by making calls to your database. > >really? this statement surprised me. So, you're suggesting that I just >recursively add the markers via addOverlay as opposed to building an >array and then adding to the marker manager?
It looks to me like you're managing your markers, by fetching them from the database when the map moves or zooms, then using MarkerManager to do essentially the same thing for you. I can't see that you gain anything by managing the markers twice, and it would go faster if you chose to use one system or the other. If the total number of markers is more than 2000, then I'd recommend using server-side management, simply because of the time required to transfer the data for 2000 markers to the client. MarkerManager will also cause you problems with toggling your categories. When MarkerManager decides that a marker should be displayed as a result of a map movement it ignores the fact that you may have previously called .hide() on that marker. [Since MM is open source, it is possible to change your copy of the code to change that behaviour.] -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
