-
-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Help: What is the proper way of controlling zIndex #38
Comments
You are doing it correctly. It's a bug (or a missing feature?) in the https://pypi.org/project/dash-leaflet/0.1.2rc1/ It you agree that it now works as intended, i'll include it in the next release :) |
I tested it and the change did the trick. thank you for your help. |
This seems to have stopped working on versions 1.0.0 and later. Could someone confirm that? Also, any other way of controlling zIndex is fine to me, with exception setting order. |
Yes, I can confirm that! I've just migrated to version 1.0.0 and the ordering of my layers inside a map that worked before stopped working now. @emilhe could you please have a look into that? |
I am trying to migrate my code from 0.0.22 to v0.1 of dash-leaflet but I am having a trouble of enforcing
zIndex
between two GeoJSON layers. In the past, I wrapped the layers in Pane and set zIndex onPane.style
property. After playing around for a bit, I noticed that zIndex is ignored and the GeoJSON layers are stacked based loading time. I created a simple example to demonstrate. By simply changing the sleep in each of the function, I change the order of the layers.In the example, I would expect the
states_slow
layer should end up bellowstates
. But because of thestates_slow
is slower to load, it ends on top and thus the focus.I admit, I have no clue what I am doing here so forgive me if I am missing something obvious. :)
Is it a bug or am I doing something wrong?
Thanks for your help.
The text was updated successfully, but these errors were encountered: