Avoid checking limits when updating both min and max for contours #26601
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.
PR summary
closes #26531
In #26531 (comment) @anntzer postulated that a better fix is possible, I'm open to one, but this works.
Note that I think there still could be some problems if updating vlims later on (this only addresses the setting in
__init__
).It was also suggested to add an atomic update of both vmin and vmax (which only triggers
changed
once), but that is not yet implemented.PR checklist