I too found that when toggling a layer off and on, the display stacking
order was lost.
The answer was to turn all layers off and redisplay the toggle on layers.
(leaving out the toggled off layers)
Even this did not work correctly as Google had cached the KML layer tiles
which kept throwing out
I should add that I used a defaultviewportchanged listener to detect when a
kml layer loaded before adding the next layer in the order.
--
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
On Mar 16, 11:10 am, daza wrote:
> Hi
>
> I have read all the post regarding order including
> thishttp://code.google.com/apis/maps/documentation/javascript/forum.html?...
>
> I'm loading 4 kml layers of polygons some of which overlap so the layer
> ordering is important.
> I can load them in the
This isn't the answer you wanted, but make sure you start this issue:
http://code.google.com/p/gmaps-api-issues/issues/detail?id=2804
Support of a z-index for kml layers would alleviate development headaches
like yours.
Chad Killingsworth
--
You received this message because you are subscribe
