|
|
Reminder sent to: alexy, nicole
Alex, Nicole, I would need your help here.
When saving the ROI, eventually vtkMRMLAnnotationStorageNode::WriteAnnotationTextProperties complains because there is no text display node.
Is text really mandatory ? Why should it matter if there is no text display node to the ROI node ?
What's the proper way to create a ROI node ?
Please look at vtkSlicerVolumeRenderingLogic::UpdateDisplayNodeFromVolumeNode to see if I create the node correctly.
Thanks for your help. |
|
|
The annotation storage nodes are a bit fragile, the writing is chained through the classes, and display nodes are required in increasing number as you get into sub classes.
The ROI derives from text nodes, as does every other MRML Annotation node, to support the display properties of text associated with an annotation. The ROI widget doesn't use text currently, though it could be a useful addition for differentiating mulitple ROIs in a scene.
In vtkSlicerVolumeRenderingLogic::UpdateDisplayNodeFromVolumeNode you're just instantiating the ROI node and adding it to the scene, but the annotation nodes tend to do important things in the Initialize method, like creating necessary display nodes, and adding themselves to the scene (which is something I've already changed in my re-write).
Short answer: try calling this in your method:
roiNode->Initialize(this->GetMRMLScene()) |
