-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vtkIGTLToMRMLImage::MRMLToIGTL don't support color images. #54
Comments
christiana
pushed a commit
to SINTEFMedtek/OpenIGTLinkIF
that referenced
this issue
Oct 6, 2015
…essage. Fixed by adding NumComponents
jcfr
added a commit
to Slicer/SlicerGitSVNArchive
that referenced
this issue
Dec 2, 2015
Fixes #4095 $ git shortlog 3ad1f67..6e297b7 --no-merges Christian Askeland (3): BUG: openigtlink/OpenIGTLinkIF#54 Color not supported in vtkImageData->igtl::ImageMessage. BUG: Fixed openigtlink/OpenIGTLinkIF#55 Segfaults in encode/decode vtkPolyData BUG: Fixed openigtlink/OpenIGTLinkIF#56 vtkPolyData encoding reuses data from last encoding. Junichi Tokuda (1): Instead of creating a new igtl::PolyDataMessage in vtkIGTLToMRMLPolyData::MRMLToIGTL() to clear the content of OutPolyDataMessage, call igtl::PolyDataMessage::Clear(). igtl::PolyDataMessage::Clear() will be reimplemented based on the discussion for Issue openigtlink/OpenIGTLinkIF#57. From: Junichi Tokuda <[email protected]> git-svn-id: http://svn.slicer.org/Slicer4/trunk@24802 3bd1e089-480b-0410-8dfb-8563597acbee
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When converting vtkImageData to igtl::ImageMessage, the NumComponents are not taken into account. There are some remnants of component support in the code, but it is commented out and missing.
I am preparing a fix for this, and will submit a pull request shortly.
The text was updated successfully, but these errors were encountered: