Skip to content

BUG: Fixed incorrect value ending up in composite view's volume node IDs

By not checking the compared object by contained values, the string 'keep-current' could end up in the volume node IDs (background, foreground, label) stored in vtkMRMLSliceCompositeNode, making it hard to check if a valid volume node in shown in a slice view.

For some reason the string 'NULL' can also end up in these char* members that should only contain valid node ID strings or null pointer, hence the fix in qSlicerSubjectHierarchyVolumesPlugin. The source of the string 'NULL' is still unknown.

Merge request reports