Hi Andreas. Thanks for the reply (and for the reply to my other post of the same day).
The reason for the extra layer for the selected features is because we want to show selected features at all scales, but the vector layer for our "locations" layer has too many features to display at all scales: it drags IE to a crawl, rendering it unusable. So for our "main", location features layer, we display only at the 10th zoom level and we display only the features within the maps current extent (requiring a callback to the server every time the extent changes) and we use a cluster strategy for it. This helps with the locations layer (sort of -- I'll be posting again shortly in another thread regarding problems we're having with the cluster strategy) but so that the user can always see all the features that they've selected, we need a 2nd vector layer (or equivalent) to display only selected features at all scales. Even given that, we've decided to hold off adding a 2nd selected features layer for to make sure we can get the cluster strategy working the way we need it first. We'll likely revisit this, but we have to resolve our other issue first... -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/vector-layer-with-highest-zIndex-not-overlaying-other-vector-layers-tp5592538p5596175.html Sent from the OpenLayers Dev mailing list archive at Nabble.com. _______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
