Difference between revisions of "Developer Meetings/20160607"

From Slicer Wiki
Jump to: navigation, search
Line 11: Line 11:
  
  
* using segmentation child classes in the segmentation editor <br>
+
* using segmentation child classes in the segmentation editor: http://slicer-devel.65872.n3.nabble.com/editor-I-O-issue-td4036752.html
http://slicer-devel.65872.n3.nabble.com/editor-I-O-issue-td4036752.html <br>
 
 
 
Use Case: having segmentation child class which can have a different defult display node respect to the segmentationDisplayNode.
 
Use Case: having segmentation child class which can have a different defult display node respect to the segmentationDisplayNode.
 
proposed solution:  
 
proposed solution:  
 
** having a method in the VolumeNode such as CreateDefaultSegmentationNode()
 
** having a method in the VolumeNode such as CreateDefaultSegmentationNode()
 
** using it in the segmentation editor: https://github.com/SlicerRt/SlicerRT/blob/master/SegmentEditor/SegmentEditor.py#L103
 
** using it in the segmentation editor: https://github.com/SlicerRt/SlicerRT/blob/master/SegmentEditor/SegmentEditor.py#L103
 +
 +
*  failure to properly handle multiple dependencies: [http://www.na-mic.org/Bug/view.php?id=4200] - blocker for mpReview users
 +
** follow-up investigation: https://github.com/commontk/qRestAPI/pull/11
 +
* failure to properly package SlicerOpenCV extension on Mac: https://github.com/SBU-BMI/SlicerOpenCV/issues/30
  
 
= Updates =
 
= Updates =
  
 
= Conclusion =
 
= Conclusion =

Revision as of 20:36, 6 June 2016

Home < Developer Meetings < 20160607



To Discuss

Use Case: having segmentation child class which can have a different defult display node respect to the segmentationDisplayNode. proposed solution:

Updates

Conclusion