> Make the infowindow smaller ; or the map bigger ; or stop using > markermanager.
Actually, forget that ; it's your own updateMarkers() code that close the infowindow when it executes - map.clearOverlays(); as an infowindow is an overlay too. I can think of a couple of approaches for you - Adapt updateMarkers() so that it only adds "new" markers and removes "redundant" markers, leaving "existing markers in viewport" well alone. You'll probably need some unique ID for your markers so that your code can do comparisons. or - Remember if an infowindow is open when you call createMarkers() and re-open it at the end. You will probably need that marker ID again for this. or - Add some padding to your XML_URI so that it fetches markers for a bigger area than the visible viewport. Alter your trigger for updateMarkers() so that it doesn't just refresh on every map moveend, but only if it moves more than X pixels, that's to say outside of that padding area. This is an effect very like markermanagers "padding" setting. cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
