Hi,
thanks for posting the fix. Is there a bug filed for it? Or has it been
integrated already?
Thanks,
Sascha
On 07/09/2013 03:46 PM, Miklos Espak wrote:
Hi Caspar,
thanks for dealing with these requests.
What regards 1. and 2., I'm not generally interested in the context
menu approach because I find the DnD much more intuitive and simple.
About 3., yes, I meant the accessibility of these properties from the
application. I made some suggestions on the ticket that affects the
property list view and the data manager. Basically, what I suggest is
that these plugins should show the render window specific property if
a render window is selected and a property is set specifically for
that, otherwise the global property. This is not compatible with the
current behaviour, though.
Another note is that in the following commit I fixed a bug in the
current drag and drop facility of MITK (for reordering the layers).
This is merely a fix, and does not change the parent-child
relationship of the nodes. The problem was that the nodes were
inserted in a wrong position at drop. (Different position if you
dragged the node upwards or downwards.)
https://github.com/NifTK/MITK/commit/cfeed4eb98462e00fe0e8fdae3ec7988ae334beb
I you could merge this, that would be very helpful. I am happy to
rebase it on the latest master and send a pull request.
Cheers,
Miklos
On 9 July 2013 12:15, Goch, Caspar Jonas <[email protected]
<mailto:[email protected]>> wrote:
Hi Miklos,
we discussed whether or not to include these features and if so
how to implement them. We would very much appreciate your input on
our ideas, especially as most of the details are very much use
case dependend.
1.Dragging and dropping is out, as it is too ambiguous and can
easily break a lot of things, but there might be another way to do
it. See *Bug 15561* <http://bugs.mitk.org/show_bug.cgi?id=15561>
2.This is a very special case we do not want to support ourselves,
but it could probably be made more easily accessible by a change
context menus work proposed in *Bug 15560*
<http://bugs.mitk.org/show_bug.cgi?id=15560>
3.We already support this possibility, there just is no way to
access it from the application as of yet. See *Bug 15562*
<http://bugs.mitk.org/show_bug.cgi?id=15562>
As stated above, we would appreciate any input from users on the
list on whether they need this kind of functionality and what
their use-cases/requirements are.
Best,
Caspar
*Von:*Miklos Espak [mailto:[email protected]
<mailto:[email protected]>]
*Gesendet:* Donnerstag, 27. Juni 2013 14:59
*An:* mitk-users
*Betreff:* [mitk-users] data manager customisation
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
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
