0003817: Loading a scene without camera produces inconsistent state

ID	Project	Category	View Status	Date Submitted	Last Update

0003817	Slicer4	Module Cameras	public	2014-08-23 13:12	2014-11-01 19:14

Reporter	finetjul	Assigned To
Priority	normal	Severity	minor	Reproducibility	have not tried
Status	acknowledged	Resolution	open
Product Version
Target Version		Fixed in Version

Summary	0003817: Loading a scene without camera produces inconsistent state
Description	Sometimes MRML scene files don't contain camera nodes (to keep those scenes short and concise). Loading such scenes may lead to view nodes without any camera node. That can potentially generate crashes because code always expects a camera node for any given 3D view.
Steps To Reproduce	Start Slicer Load scene file with no Camera XML element Close scene Load same scene file again -> open python console and c = slicer.mrmlScene.GetNodeByID('vtkMRMLCameraNode1') c.GetActiveTag()
Additional Information	Regression from 0002758 It is likely due to the commented lines in vtkMRMLCameraDisplayableManager::UpdateCameraNode(): vtkDebugMacro("why am I here? I have a camera node already!" << unassignedCamera->GetID() << " for view node " << viewNode->GetID()); //unassignedCamera->SetActiveTag(viewNode->GetID()); //this->SetAndObserveCameraNode(unassignedCamera);
Tags	No tags attached.

Date Modified	Username	Field	Change
2014-08-23 13:12	finetjul	New Issue
2014-08-23 13:12	finetjul	Relationship added	related to 0002758
2014-11-01 19:14	jcfr	Status	new => acknowledged