View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001869||Slicer4||Module SceneViews||public||2012-04-06 10:51||2017-07-24 22:48|
|Product Version||Slicer 4.0.0|
|Target Version||backlog||Fixed in Version|
|Summary||0001869: Unfriendly behavior of scene views 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.
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.
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
ERROR: In /Users/fedorov/Slicer/Slicer4/Libs/MRML/Core/vtkMRMLScene.cxx, line 1379
ERROR: In /Users/fedorov/Slicer/Slicer4/Libs/MRML/Core/vtkMRMLScene.cxx, line 1387
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
Short discussion pre 4.4 release: think about adding an import scene view functionality. But I don't have the resources to work on this for 4.4.
See related discussion at https://discourse.slicer.org/t/what-scene-views-are-supposed-to-do/497
This issue has been long been unresolved, but should be resolved eventually.
|2012-04-06 10:51||fedorov||New Issue|
|2012-04-06 10:51||fedorov||Status||new => assigned|
|2012-04-06 10:51||fedorov||Assigned To||=> nicole|
|2012-04-09 14:40||nicole||Note Added: 0003992|
|2012-04-09 14:48||fedorov||Note Added: 0003993|
|2012-04-30 13:41||fedorov||Note Added: 0004114|
|2012-04-30 13:46||fedorov||Additional Information Updated|
|2012-05-01 05:16||fedorov||Relationship added||parent of 0001960|
|2012-08-20 10:39||nicole||Target Version||=> Slicer 4.4.0|
|2014-03-06 11:09||nicole||Note Added: 0011261|
|2014-03-06 11:09||nicole||Status||assigned => acknowledged|
|2014-03-06 11:09||nicole||Target Version||Slicer 4.4.0 =>|
|2017-06-15 11:47||lassoan||Summary||Unfriendly behavior handling new scene elements => Unfriendly behavior of scene views handling new scene elements|
|2017-07-24 22:46||lassoan||Note Added: 0014947|
|2017-07-24 22:48||lassoan||Product Version||=> Slicer 4.0.0|
|2017-07-24 22:48||lassoan||Target Version||=> backlog|
|2017-07-24 22:48||lassoan||Note Added: 0014949|