[FIX] Select Rows: Fix incorrectly stored values in settings #4798
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.
Issue
Select Rows stored values of discrete variables as indices. If the data changed so that values were reordered, it chose wrong values. If values were removed, it could crash with index out of range.
To reproduce, construct File -> Select Rows -> Select Rows. Load Iris, obviously.
After this the second Select Rows will have selected the (originaly) third (now second) Iris type.
Alternatively:
This will crash the second Select Rows widget.
Description of changes
DomainModel
for combos.Variable
; context handler converts this to the usualstr, int
presentation. With this, the context handler has an instance of variable, which it needs to see the values.int
is done in context handler to minimize the changes to the widget's code.Includes