Page MenuHomePhabricator

Save MITK Project messes up the order of nodes
Closed, ResolvedPublic

Description

I have a number of nodes in the datamanger.
Their order is important for the rendering! e.g. when a segmentation node is UNDER (not a child node, simply lower in the datamanager list) the base image, the segmentation is not visbile!

When you save the MITK Project and load it again, the position of the nodes in the datamanger changes!

You can take this as an example project:
t:\temp\P0031-T4.mitk

Change the positions, save the MITK project again, load it and you will see the position of the nodes changes.

It should not.

Event Timeline

This bug is really disturbing when storing many items. If you want to show images/objects to a physician, it is helpful to create a big project file with many items, which then can be assessed very fast item by item without interrupts like loading or searching files. In this case a manual reorganisation of all data nodes can easily take more than 10 minutes, especially if an alphabetical order is desired.

Joseph have you talked with Daniel about this issue? Would be nice if this bug can be fixed during the upcoming release.

New remote branch pushed: bug-11181-messedUpNodeOrder

Fixed:
The layper property of the saved scene is now corretly used to order the nodes when loading a scene file => saved order is restored.

Michael could just clean up the code? There are some uncommented code parts included which should be removed.

[1a2964]: Merge branch 'bug-11181-messedUpNodeOrder'

Merged commits:

2012-12-07 14:42:55 Michael Brehler [e215b4]
removed commented code-segments


2012-12-05 17:28:32 Michael Brehler [c884c2]
Solved.

[c76848]: Merge branch 'bug-11181-messedUpNodeOrder'

Merged commits:

2012-12-10 20:37:47 Michael Brehler [fdcd29]
COMP: Works for me now.