|Anonymous | Login | Signup for a new account||2013-12-04 12:34 EST|
|Main | My View | View Issues | Change Log | Roadmap | Docs|
|Viewing Issue Simple Details|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0001869||[Slicer4] Module SceneViews||feature||N/A||2012-04-06 14:51||2012-08-20 14:39|
|Summary||0001869: Unfriendly behavior handling new scene elements|
If I create a scene view, and then add a new data element (say, a volume), it will disappear from the scene if I switch to the scene view I created earlier.
I find this behavior very inconvenient. Also, it contradicts the very name of the function: in my understanding "Scene View" should be a "view" of the data, and should not modify the collection of data items included in the scene.
|Additional Information||Per discussion with Ron, the correct behavior he expects is to retain newly added elements in the scene, while switching to scene views created before those items were added.|
|Tags||No tags attached.|
|The scene views have always worked this way. The change that I can see being useful is to prompt you to save a scene view before switching to one that has nodes removed. Ron had me add a scene view whenever the mrml scene is saved to disk, so if you've loaded the scene from file, you can always get back to that scene view.|
> The scene views have always worked this way.
I know. That's why I submitted the same issue for Slicer3 back in the days.
My point is I don't see what is the motivation for scene views to work this way. This is very un-useful.
I understand I can save and go back, but this makes the scene with scene views essentially "read-only", meaning it cannot be ever augmented with new data. What is the user-level use case justifying this behavior?
as of r19932, the following sequence of steps leads to a crash:
1) load sample dataset, 2-over-2 layout
2) create a scene view
3) switch to 4-up layout
4) add a fiducial
5) create another scene view
6) switch to scene view (2)
ERROR: In /Users/fedorov/Slicer/Slicer4/Libs/MRML/Core/vtkMRMLScene.cxx, line 1379
vtkMRMLScene (0x112d3b9b0): RemoveNode: Node vtkMRMLAnnotationPointDisplayNode/AnnotationPointDisplay[0x14a4dfb90] already removed
ERROR: In /Users/fedorov/Slicer/Slicer4/Libs/MRML/Core/vtkMRMLScene.cxx, line 1387
vtkMRMLScene (0x112d3b9b0): RemoveNode: class: vtkMRMLAnnotationPointDisplayNode name:AnnotationPointDisplay id: vtkMRMLAnnotationPointDisplayNode1[0x14a4dfb90] can't be found by ID
ASSERT failure in qMRMLSceneModel::onMRMLSceneNodeAboutToBeRemoved(): "A node has been removed from the scene but the scene model has never been notified it has been added in the first place. Maybe vtkMRMLScene::AddNodeNoNotify() has been used instead of vtkMRMLScene::AddNode", file /Users/fedorov/Slicer/Slicer4/Libs/MRML/Widgets/qMRMLSceneModel.cxx, line 1131
|2012-04-06 14:51||fedorov||New Issue|
|2012-04-06 14:51||fedorov||Status||new => assigned|
|2012-04-06 14:51||fedorov||Assigned To||=> nicole|
|2012-04-09 18:40||nicole||Note Added: 0003992|
|2012-04-09 18:48||fedorov||Note Added: 0003993|
|2012-04-30 17:41||fedorov||Note Added: 0004114|
|2012-04-30 17:46||fedorov||Additional Information Updated|
|2012-05-01 09:16||fedorov||Relationship added||parent of 0001960|
|2012-08-20 14:39||nicole||Target Version||=> Slicer 4.4.0|
|Mantis 1.1.4[^] Copyright © 2000 - 2008 Mantis Group|