View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003590 | Slicer4 | Core: MRML | public | 2014-02-14 10:23 | 2014-02-26 06:18 |
Reporter | finetjul | Assigned To | alexy | ||
Priority | normal | Severity | minor | Reproducibility | sometimes |
Status | assigned | Resolution | open | ||
Product Version | Slicer 4.3.1-2 | ||||
Target Version | Fixed in Version | ||||
Summary | 0003590: Storage node should be created when needed | ||||
Description | Right now, to save a node, it needs a storage node. It is currently done in the Save Data Dialog. However, when requesting a node to be saved programmatically (C++ / Python) directly via the ioManager (using dialogs or not), the storage node is not created which silently fail to be saved. | ||||
Tags | No tags attached. | ||||
Can this operation be moved from the dialog into a mrml logic class? Creating a default storage node and adding it to the scene seems like a common operation. https://github.com/Slicer/Slicer/blob/master/Base/QTGUI/qSlicerSaveDataDialog.cxx#L484 |
|
I think it should be moved. Maybe we need to create a vtkMRMLStorageLogic. |
|