fix(segmentation): Fix issue exposed by interpolationContourSegmentation example #2322
Merged
Merged
Conversation
…vailable segment if none is currently set.
sedghi
approved these changes
Sep 11, 2025
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
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.
Context
Run the https://www.cornerstonejs.org/live-examples/interpolationcontoursegmentation example. Notice that an exception is thrown when clicking on an image to apply a segmentation to it.
Using
git bisectI was able to determine that #2231 caused this issue.Changes & Results
Initialize the active segment index to the first available segment if none is currently set.
Testing
Run the example. It should behave as expected.
Checklist
PR
semantic-release format and guidelines.
Code
etc.)
Public Documentation Updates
additions or removals.
Tested Environment