-
Notifications
You must be signed in to change notification settings - Fork 79
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
Rendering way of type "_route" is masked by bridges #1478
Comments
Strange: In the standard configuration (standard.oss) in include/route.oss you can find:
Important in context is the See also Which should result in the route being the last entry in the way render list, thus rendering on top of everything else. Looking at the code however, it seems like the way needs to have a "high" layer value for this, too, to be rendered after "lower" layers like bridges (which should have low positive values). In the Qt code, the initialization for the route is done in OverlayObject.cpp/OverlayWay::toWay (and functions called from there). In the header, you see that Overlay objects have
:-) I assume some of these internal "tricks" are missing in your code? |
@Karry : Right? We also have zIndex. I do not remember the purpose of this one. Karry, can you help? We should also document it ;-) |
Just see "Section ORDER WAYS" in our documentation
And yes, in Qt, I just setup layer to maximum for "overlay" objects. Regarding zIndex, it is really missing in documentation. Looking to stylesheets, it seems to me that it is used just for way decorations - to render outlines first. With that, I would guess that zIndex is used as last property for sorting (just order individual lines for the same way), but looking to the code, sorting order is: layer, zIndex, style priority, style sheet priority (ORDER WAYS). Should we change it? |
Thank you @Framstag and @Karry for the hints, I checked all this in my code, tried to use the standard.oss stylesheet from the distribution but the rendering is still the same...
|
I am missing |
Thank you @Karry, this is the solution ! |
I don't know if it is a error in the usage of the library on my side or a issue in the lib ?
The text was updated successfully, but these errors were encountered: