Hi,
I would need some customisations on the data manager plugin.
What would be the most straightforward way of this without diverging from
the MITK upstream too much?
I already implemented some of the required features in a fork, but they
cannot be easily pulled into MITK in their current form, and I am also not
sure if you want those changes.
The features would be:
1. Drag and drop of nodes within the data manager to make nodes "derived".
E.g. you could pull a segmentation upon a reference image, it would be made
its derived node.
2. If a 3D segmentation would be pulled on a 4D image then a 4D
segmentation would be created in which the original segmentation would be
propagated along time.
2. Make the check boxes show the render window specific visibility of a
render window instead of the global visibility. This would be need for our
DnD display in which you can watch different set of images in different
viewers side by side. But currently you cannot see in the data manager
which viewer shows which images. I can imagine a "SetCurrentRenderWindow"
function in the data manager view. If the current render window is set then
the would show / control its specific visibility properties, and if it was
set to NULL then the global visibility properties.
Would any of these be of your interest?
Cheers,
Miklos
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
