View Issue Details

IDProjectCategoryView StatusLast Update
0002623Slicer4Module VolumeRenderingpublic2014-05-13 11:36
ReporterfinetjulAssigned Tofinetjul 
PrioritylowSeveritytrivialReproducibilityN/A
Status feedbackResolutionopen 
Product VersionSlicer 4.1.1 
Target VersionFixed in Version 
Summary0002623: Change vtkMRMLVolumeRenderingDisplayableManager::DisplayNodes from map to vector
Description

Potentially the ID of a node can change, if the displayable manager doesn't track that change (vtkMRMLNode::IDChangedEvent), then it shouldn't use the ID as a unique key.
-> use a simple vector and browse the vector and comparing the node ID with the node->GetID().

TagsNo tags attached.

Relationships

related to 0002628 acknowledgedfinetjul VR displayable manager should not show display node that are not referenced by displayable node 
child of 0002621 closedfinetjul Switching to VR after manually creating display node causes crash 

Activities

jcfr

jcfr

2014-05-13 11:36

administrator   ~0011807

May be MRML References could be used here ?

Issue History

Date Modified Username Field Change
2012-10-07 18:06 finetjul New Issue
2012-10-07 18:06 finetjul Status new => assigned
2012-10-07 18:06 finetjul Assigned To => finetjul
2012-10-07 18:06 finetjul Relationship added child of 0002621
2012-10-08 21:13 finetjul Relationship added related to 0002628
2013-08-09 04:30 finetjul Target Version Slicer 4.3.0 => Slicer 4.4.0
2014-05-13 11:36 jcfr Note Added: 0011807
2014-05-13 11:36 jcfr Status assigned => acknowledged
2014-05-13 11:36 jcfr Target Version Slicer 4.4.0 =>
2014-05-13 11:36 jcfr Status acknowledged => feedback