Wasn't it Drew who wrote: > >How do you know when the processing is done?
With GGeoXml you don't know. If you've got lots of markers, you probably already notice that creating your sidebar your way is pretty slow (except in Google Chrome) because the whole sidebar has to be re-rendered each time the innerHTML changes, and in some browsers that's quite slow. If you were to perform the sort() and regenerate the whole sidebar each time a new entry arrives, it would run even slower. Even if speed isn't a consideration, it might be a little disconcerting to a user if the entry that they're intending to click keeps getting moved down the list as new entries arrive above it. You might consider setting a timeout for a few tenths of a second. If another entry arrives before the timeout triggers, perform a clearTimeout() on the existing timeout and create a new one. When the timeout gets triggered, create the sidebar. This strategy may end up sorting and rendering the sidebar more than once if there's a delay in the messages from the GGeoXml server, but that might not be altogether a bad thing. -- 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 -~----------~----~----~----~------~----~------~--~---
