That was a very promising tip. However, on experimentation, it seemed that the event fires before the tiles are actually rendered. I suspect that "loaded" means collected from the server rather than processed by the javascript. Still, this would be useful in conjunction with setTimeout to allow for slower upload times. Right now, I am using a 1500 ms timeout. If I used that event thingie, I could probably trim that quite a bit.
Thanks On Sep 19, 7:03 pm, Martin <[email protected]> wrote: > You could add an event listener for the 'tilesloaded' event: > > http://code.google.com/apis/maps/documentation/javascript/reference.h... > > "This event is fired when the visible tiles have finished loading." > > You'd need to keep a reference to the listener so that you can remove > it after creating your overlays else it'll fire each time the map is > panned/zoomed and the tiles load. > > Martin. > > On 19 Sep, 21:59, Michael M - As You Wish <[email protected]> > wrote:> Okay! The setTimeout function worked just great. > > > It's a little bit of a kludge, I suppose, and the more elegant way > > might be to get something to key of a "Map is all pretty now" event, > > but this works good. I think the only drawback will be to select a > > timeout that works for most browsers and systems. Or say heck, if > > their computers are slower than mine, to heck with them... > > > But that's not nice, is it? > > > m -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=en.
