William, Thanks for the suggestion.
1. This file listens to map for defaultviewport_changed http://www.mappingsupport.com/forum_post/kml_71.html The event never fires and the map div remains hidden 2. This file listens to mykml for defaultviewport_changed http://www.mappingsupport.com/forum_post/kml_72.html The event never fires and the map div remains hidden The above two outcomes make sense. The event defaultviewport_changed is specific to KML files and apparently the KML viewport cannot *change* until a KML viewport is first established. I also tried the event "bounds_changed" 3. This file listens to map for bounds_changed http://www.mappingsupport.com/forum_post/kml_73.html The event fired 3 times At one point something flashed on the screen After the 3rd event a map with the KML data appeared 4. This file listens to mykml for bounds_changed http://www.mappingsupport.com/forum_post/kml_74.html The event never fires and the map div remains hidden #3 above is not satisfactory since my goal is to have nothing flash on the screen until the map with the KML data appears. I also tried setting the initial latitude to 85 but that just produced a screen where each tile held the message "Sorry, we have no imagery here". The KML never displayed. Any other thoughts on what I might try to achieve my goal of having the KML map appear on the screen without anything else first flashing on the screen? Gee, I sure wish I could listen to mykml for tilesloaded...... -- 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 google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
