- User Since
- Aug 1 2016, 12:10 PM (132 w, 5 d)
Wed, Feb 13
Mon, Feb 11
Fri, Feb 8
Mon, Feb 4
Fri, Feb 1
Pushed new branch T25977-Shortcuts-for-multilabel-segmentation.
Thu, Jan 31
Tue, Jan 29
Fri, Jan 25
Wed, Jan 23
Jan 14 2019
Jan 10 2019
Jan 7 2019
Jan 2 2019
Just stumbled upon this. Could you clarify what you expect to happen? Has this been solved in the meantime?
Using the new option "Use selected images", the mitk::LevelWindowManager::SetSelectedImages-function defines a set of selected images (according to the 'selected'-property) but uses the last image of the set of selected images as the 'currentImage'.
Please note that QmitkLevelWindowWidgetContextMenu::OnUseAllGreyvaluesFromImage() and QmitkLevelWindowWidgetContextMenu::OnUseOptimizedLevelWindow() use the mitk::LevelWindowManager::GetCurrentImage()-function and will therefore adjust the level window according to the current image.
Dec 21 2018
The level window can now be applied to a set of selected data nodes (if using the new option "Use selected images" in the level window slider context menu).
The 'selected' property of a data node has to be set, though. This is done e.g. in the data manager.
Using the new selection concept the selected property is currently not maintained and therefore using the new selection widgets will not allow to use selected nodes for the level window slider (see T25804).
Using T25483 it is now possible to choose setting the level window (slider) for the selected data node.
Pushed new branch T25483-Level-window-for-selected-images.
A first draft is implemented with a single selected image and it works quite well.
Dec 19 2018
Dec 17 2018
- be able to copy segmentation maps from one slice to another. Rational behind this: segmentation map for a structure of interest might be missing not only in the current but also in the neighboring (spacial and temporal) slices. The segmentation map is then likely to be similar in these slices. Being able to copy with lead to more consistent segmentation maps.
Dec 14 2018
My initial thought was that I accidentally fixed a bug with the new context menu actions so looking closer into the original opacity-slider action in the old data manager might reveal the flaw that is responsible for this behavior.
Something like - not correctly setting the opacity using the opacity value from the data node when opening the context menu.