In order to simulate the data manager view, the render window manager should show a tree view and use a tree model to display its render window specific data nodes.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T28578 [mxn multi widget] Optimization of the mxn multi widget | ||
| Wontfix | kalali | T26394 [Render window manager] Provide tree view / model |
Event Timeline
Comment Actions
Removing a node on 1. level with child nodes is not correctly reflected in the currently selected render specific tree. The tree model is updated with all data nodes of the data storage before the remove-process is finished so the data storage still contains the to-be-removed- data node.
If this also happens in the QmitkDataStorageSimpleTreeModel needs to be investigated.
Comment Actions
Sometimes adding a new segmentation will not show the segmentation -> layer / tree problem? Need to investigate further.
Comment Actions
This is then based on the QmitkDataStorageTreeInspector? Would make sense, wouldn't it?
Comment Actions
If I remember correctly I created a new renderwindowtreemodel, based on QmitkAbstractDataStorageModel because I could not reuse the classic tree inspector. Reason for this was probably mainly the different handling of data nodes for specific render windows. I will re-recheck this within the next weeks and probably come back to you for consultation ;)
This T26399: Workbench crash on simple tree model update might also be related.
Comment Actions
This task is invalid; related work will be continued in T29297: [mxn multi widget] Optimize data accessibility inside render windows.