Visibility Property mismatch in EpiNav and NifTK
Problem: If a dataset is saved as a .mitk in EpiNav and then loaded in NifTK node visibility cannot be changed.
Reason: EpiNav assigns visibility properties to each render window separately (this is a feature to allow independent display of objects in 2D and 3D render windows). This properties is then saved in the .mitk.
NifTK only assigns one visibility property that is global. The rendering pipeline finds the render window specific property saved from EpiNav and uses this to determine visibility.
Potential solutions: In EpiNav do not save the render window specific visibility properties. In NifTK remove the render window specific visibility tags when data nodes are added to the data manager.