OK, I have now solved the windows info problem with the following settings : iwwidth:40, iwheight:5 With iwheight at 5, the "multigeometry" is hidden.
Concerning speed, I use almost exclusively Firefox and it does not slow down significantly the loading (less than 10 sec). Then, selecting a track is quite fast (2 to 3 sec) and navigating the map is smooth and fine with fast updating of the map and tracks. This is why I said speed was not a priority in my case. In fact, it is faster than the Nineveh Archives page I used as sample for my own page, which is great. However, I just come to test the same with IE and it is something like an other planet. First of all, the page takes ages to load completely (20 sec for the fastest, up to 1.5 min for one test !). Then selecting a track takes an other big share of time, the information windows is also long to appear while updating of the map when navigating is quite slow. All together, it is a completely different story with IE ! The same Nineveh Archives is also extremely long to come up and does not load completely either (menu is only showing check boxes without text) All other example sites given on the GoeXml project page give significant advantage to Firefox against IE in term of loading time and navigation. Is there anything wrong between IE and Google API, KML files and so on, or with GeoXml itself and is there something to be done on IE to boost it ? This really is annoying me. Thank you for your feedback on the IE "dark side". -- 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.
