Add zIndex support to L.TileLayer #837
Conversation
| @@ -12,6 +12,7 @@ L.TileLayer = L.Class.extend({ | |||
| subdomains: 'abc', | |||
| errorTileUrl: '', | |||
| attribution: '', | |||
| zIndex: 0, | |||
There was a problem hiding this comment.
Maybe it shouldn't be set by default at all?
There was a problem hiding this comment.
Yes, could remove this, as it is effectively zero anyway I think? I thought I should add a default value in the options as it makes it explicit what z-index the tile layers will have by default.
There was a problem hiding this comment.
I want to leave it not set so that I could add automatic setting of zIndex for layers that don't have it explicitly set in future (maybe in order they're added to the map).
|
While I plan to implement a more extensive zIndex support in 0.5, this may be a good temporary solution, although it doesn't work with the current |
|
I could modify the "bring" methods to iterate through the tile layers and find the maximum/minimum z-index and assign a new z-index based on that. |
|
I'll merge it in a separate branch and try fiddling with it and eventually merge into master, no need to add anything. Thanks! |
|
Check it out cdfaad9 |
|
Thanks, looks great! |
I had a problem where I needed to have three tile layers displayed in a strict order:
The street and marker WMS overlays can be toggled on and off by the user, so having a z-index set on each layer allows this order to be maintained as they are added and removed from the map.