703 - Set print layer zIndex to -200 #4387
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch sets the zIndex of the layers created by the GMF print component to -200, just like the the background layers.
The issue that was happening with Cartoriviera is that the "Plan Cadstral" BG layer has a child with "printLayers" defined. From what I understand this child is used when printing instead of the original first child. OpenLayers Layer object are created in the GMF print componnent, but were not given a zIndex, i.e. it stays as 0. When issuing a print requests, layers are ordered by zIndex, then reversed. That print layer was therefore put on top.
There's currently no way to test this using the demo server. I also don't have a lot of knowledge of the print tool, so I don't know if this will have an impact somewhere else.