[WFS provider] Avoid dangling download progress dialog #30039
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
rouault
added
backport release-3_4
Bug
While investigating qgis#27384, which I failed to reproduce, I noticed another - minor - issue when loading layers from a local GeoServer instance. Very often (easily triggered by reloading layers with F5), one or several download progress window would be displayed ~ 4 seconds after the refresh had finished. This was due to a race between the creation and destruction of this window.
rouault
force-pushed
the
wfs_fix_ghost_progress_dialog
branch
from
99bd3a7
to
d772210
Compare
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.
While investigating #27384, which I failed to reproduce, I noticed
another - minor - issue when loading layers from a local GeoServer
instance. Very often (easily triggered by reloading layers with F5),
one or several download progress window would be displayed ~ 4 seconds
after the refresh had finished. This was due to a race between the
creation and destruction of this window.