Closed karmflo closed 10 months ago
I believe that this is a regression (a bug in the new implementation, where the pane information is not propagated correctly to the underlying GeoJSON object). I have implemented a fix for it now. Could you test this release resolves your issues?
Thanks for you help! Works like a charm! :)
Thanks a lot
Great! I have included the changes in the (non-rc) 1.0.15 release :)
I am currently updating my application which includes migrating dash-leaflet from 0.1.28 to 1.0.13. There are several
GeoJSON
layers that need to be displayed (ordered) inside a map. The order is very important. In version 0.1.28 the ordering worked fine withdl.Pane
andstyle={"zIndex": 100}
. After migrating I noticed that zIndex is ignored and the GeoJSON layers are stacked based on loading time. Also when hovering over a layer that is in the background it will move to the top.My application uses the following updated versions:
I have also tried to play around with the
pane
option of the dl.Pane and dl.GeoJSON component which states:pane (string; optional): Map pane where the layer will be added.
, but the ordering ist still ignored.I use a very simple example to demonstrate the issue. By changing the sleep in each of the function, I change the order of the layers.
Am I missing something or is this a bug? Thanks for your help