> It's definitely map API related but maybe more of an issue with > browser/javascript functionality,
Definitely not map API related, it's all about browsers that don't multi-task very well - whatever the tasks are. In this case you want to run some data-fetching and processing script, use a 3rd party javscript (the maps API) to do some stuff (and which may do its own data fetching e.g. tiles), and allow the browser to update its display all at the same time. Some browsers will stick with running one thread until exhausted, rather than allow several threads slices of time. As Larry says, you need to add some breathing spaces in the flow to allow execution control to change to some other process. Sometimes adding some short or even zero setTimeout calls into the processing allows control to change hands. Some background http://dev.opera.com/articles/view/timing-and-synchronization-in-javascript/ In the absence of a link, we can't tell if you are having the maps API add unnecessary work e.g. by setting a map centre ahead of data availability. It's possible to do tricks like initially setting centre to the polar regions at high zoom to reduce tile fetching before you do a "real" centre. -- 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.
