Thanks. I think that will be a good solution. I did put a code delay in after the first polygon kml is called and it solved the "having to refresh to get the layer" problem. I'm looking at using that metadata_changed event and how to implement it.
On Nov 19, 2:27 am, Rossko <[email protected]> wrote: > > I'd still like to know why I couldn't get > > the marker kml to render over the polygon KML in IE. Worked fine in > > KmlLayer is an asynchronous remote service. The order you write > things in at the client is not necessarily the order that the KML is > fetched from your server, or parsed at Google's servers, or delivered > back to the client. > > One approach to retain control, is to trigger the next KmlLayer > construction at the end of each previous > one.http://groups.google.com/group/google-maps-js-api-v3/browse_thread/th... -- 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.
