Difference between revisions of "Developer Meetings/20150224"
From Slicer Wiki
| Line 5: | Line 5: | ||
*** on scene view creation/save to disk creating unique file names for storage nodes in the scene views | *** on scene view creation/save to disk creating unique file names for storage nodes in the scene views | ||
*** on scene view restore, triggering read from disk to update data | *** on scene view restore, triggering read from disk to update data | ||
| + | *** on MRB load, not deleting the temporary directory so that it can be read from | ||
== Conclusion == | == Conclusion == | ||
Revision as of 22:22, 23 February 2015
Home < Developer Meetings < 20150224To discuss
- Scene views and MRBs, specifically regarding fiducials as described in this issue.
- Fiducials have transitioned back to being stored on disk in files (one per list) rather than in the mrml scene file. This means that when they appear in scene views, the data that is stored on disk does not get updated on scene view restore, so fiducial position, visibility etc don't change. This highlights the issues in this issue about having to be either more clear about what scene views are (currently restrictued to viewing options), or changing Slicer to support different data in scene views (updated models, changed volumes, moved fiducials, etc). This would at the minimum require:
- on scene view creation/save to disk creating unique file names for storage nodes in the scene views
- on scene view restore, triggering read from disk to update data
- on MRB load, not deleting the temporary directory so that it can be read from
- Fiducials have transitioned back to being stored on disk in files (one per list) rather than in the mrml scene file. This means that when they appear in scene views, the data that is stored on disk does not get updated on scene view restore, so fiducial position, visibility etc don't change. This highlights the issues in this issue about having to be either more clear about what scene views are (currently restrictued to viewing options), or changing Slicer to support different data in scene views (updated models, changed volumes, moved fiducials, etc). This would at the minimum require:
