Cache result of checking whether axis should be inverted for wms layers #1222
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
…rs. Greatly improves speed of connecting to wms layers when a wms server has many available layers.
jef-n
added a commit
that referenced
this pull request
Mar 4, 2014
Cache result of checking whether axis should be inverted for wms layers
|
@jef-n Thanks Jürgen, Am I ok to push this to the 2.2 branch? It's affected by the same issue. |
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 greatly improves speed of connecting to wms layers when a wms server has many available layers. Currently, when I try and connect to a wms which contains ~1000 layers QGIS hangs for a couple of minutes. This hang occurs both when connecting via the add wms layer dialog and after actually adding a wms layer to the map. With this change there's only a couple of seconds wait for connecting/adding layers.
I've also commented out some debug messages which were flooding the log.