Image reslice multi component #3158
Merged
Conversation
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
BREAKING CHANGE: getTransferFunctionHash becomes getTransferFunctionsHash It takes a list of functions as argument instead of a single function Also ImageResliceMapper doesn't wieght color using mix.
1 task
floryst
added a commit
that referenced
this pull request
Jun 13, 2025
|
🎉 This PR is included in version 34.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
See #3137.
It adds the same kind of support for multi image, but for the vtkImageResliceMapper.
The vtkImageResliceMapper now supports up to 4 inputs, each representing a component.
The first volume property will be used for all rendering properties except interpolationType.