I'm having the 'zindex' problem with kmllayers and have looked at a couple of the suggestions regarding adding listeners...
Using multple poly-lines, I'm still having the same layering problem. It seems like the larger layers are on top of the smaller ones no matter how I order it, even when using the doco suggested 'kmlManager' approach. I then grabbed the CTA and the tri/hex polygon code and while it looked like it worked, when I switched the kml.addLayer order I got no change at all. Was this broken with an API update? Perhaps I'm just not getting the issue. My main goal is to have a large fiber path displayed with a smaller path denoting progress on top of it, allowing our engineering firm to update the progress path. what actually happens, though, is you can't see the progress path because the large fiber path is always on top, no matter what order I place it into 'kml.addLayer' -frank -- 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-v3@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.
