When you say "node change" what do you mean? SceneView node uses Copy method to restore the state of nodes in the scene. So it should restore all information that is copied by Copy method. However for "large data" nodes such as Volumes and Models, Copy method does "shallow copy", it does not copy ImageData or PolyData. This is done intentionally to avoid duplication of large structures since Copy is also used for Undo/Redo functionality. As the result SceneView::Restore() does not restore ImageData and PolyData. That is a limitation, and this decision was made earlier when I implemented this functionality.

If you meant something else please provide more details.

vtkMRMLSceneViewNode::RestoreScene() doesn't necessarily "copy" its nodes into the main scene, but it "add" its own nodes into the scene:
https://github.com/Slicer/Slicer/blob/master/Libs/MRML/Core/vtkMRMLSceneViewNode.cxx#L486

Fixed SceneView to add a copy of it's internal node rather than the node itself to the scene on RestoreScene()

Fixed in r20066:
http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=20066

Alex:

The test vtkMRMLSceneViewNodeRestoreSceneTest is failing on my machine
on line 121. Looking at it it seems to expect a wrong result. If you
restore a SceneView with the volume node that didn't have displayable
before you saved a SceneView it should not have a display node, but
the test expects otherwise. Am I missing something?

Julien :

Hi Alex,
If you look at createScene, it is associating a display node " vtkMRMLScalarVolumeDisplayNode1" to the displayable node ("vtkMRMLScalarVolumeNode1")
So when you StoreScene, it should save the association. RestoreScene() should make sure it is still true. This is what the first RestoreScene() (line 113) does. You can check it works by doing restoredVolumeNode->GetDisplayNodeID() at line 117.

Alex:

Sorry, I missed the creation function.
So does the test fail intentionally currently to demonstrate the problem in
http://www.na-mic.org/Bug/view.php?id=1993
?

Julien:

yes.