Page MenuHomePhabricator

Create a way to change the parent child relationship from the application
Closed, WontfixPublic

Description

Currently there is now way to change the parent-child relationships between nodes applicationside.

There are some cases where this might be desirable, although in most cases a plugin giving the option to select multiple images might work as well.

Miklos, maybe you can fill us in on any specific use cases you have in mind?

Changing the hierarchy can have very dire consequences if certain plugins expect the derived images to have specific properties similar to their parents (such as similar image geometries etc.). So it might be advisable to make this option available on a case by case basis.

Would an extended context menu work for you, where you e.g. select two nodes in the datamanage and get the option to change the parent-child relations on a right click?

This ties into T15560

Event Timeline

A use case:

I have a plugin that creates a segmentation for a reference image. The segmentation image is a child of the reference image. The plugin expects this, i.e. if you click on the segmentation it finds the reference image among its parents, so you do not need to select both image in the data manager by Ctrl-Left click.

There is a requirement that you should be able to open an already created segmentation and re-edit it. However, if you save the segmentation and reopen it, it will get into the top-most level, so the plugin will not find a reference image among its parents.

Of course, the plugin could be changed in such a way that it handles multiple selection, but I think, it's a bit inconvenient. Another advantage of being the segmentation a derived node is that then it appears as a sub-node in the data manager, so you can easily tell just by looking at the data manager which image does it belong to.

The context menu approach is also a possible option, but I find it a bit contra-intuitive. The DnD is pretty simple for the user, it works well, I have not found any drawbacks for now.

kislinsk claimed this task.
kislinsk added a subscriber: kislinsk.
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.