Merged
Conversation
Collaborator
|
This change fixes the issue. The figure below shows the display with this new version of plopp 
|
celinedurniak
approved these changes
Feb 19, 2026
Collaborator
celinedurniak
left a comment
celinedurniak
left a comment
There was a problem hiding this comment.
This change fixed the issue with the display as shown in the comments.
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.
The value-based (V) cut in 3D views was leaving out the upper bound.
Users would expect the upper bound given by the slider handle to be included in the selection (see also #526).
Example: data containing all zeros except one value = 100: the max value is left out of the selection
We fix this by using
<=instead of<in our selection.