GUI: propagate previously defined where option value#5747
Merged
landam merged 2 commits intoOSGeo:mainfrom May 23, 2025
Merged
Conversation
landam
changed the title
echoix
approved these changes
May 22, 2025
landam
added
backport to 8.4
landam
added a commit
that referenced
this pull request
May 23, 2025
landam
removed
the
backport to 8.4
This file contains hidden or 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
2 participants
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.
Previously defined value for
whereoption is not propageted.Steps to reproduce:
Create model which contains a tool with a
whereoption (see attached model select.gxm.zip)Define
whereoptionClose dialog
Re--open dialog
A
whereoption is emptyThe PR solves this bug: