The QmitkNodeSelectionDialog is the main widget to be used in order to select data nodes from the data storage. It is a pop-up-dialog that can be included in any other widget, such as the QmitkSingleNodeSelectionWidget or the QmitkMultiNodeSelectionWidget. It uses a tab widget that holds different data storage inspectors. A data storage inspector shows the (possibly filtered) data nodes of the data storage and allows to select one or more nodes. The selection can be accepted inside the node selection dialog and will be send to the including widget (i.e. the single node selection widget).

Has been solved in D328

Separate sections of feature highlights like

• DICOM image reader by default only condenses images with the same series instance UID into a 3D+t image. You may change to old behavior (condense everything where the geometry fits) in your reader configuration by setting onlyCondenseSameSeries to false in the configuration XML or by using the SetOnlyCondenseSameSeries() method of mitk::ThreeDnTDICOMSeriesReader.

Item 3 and 4 are already mentioned in separate tasks: T27474 and T27475

The error mentioned in the comment does not occur anymore in the latest develop branch.

Thanks @aguilera for extensive testing of report generation. The residual issues from this task will be handled in T27494.

• The following functions inside the QmitkStdMultiWidget have been removed
  • SetWidgetPlaneModeToSlicing
  • SetWidgetPlaneModeToRotation
  • SetWidgetPlaneModeToSwivel
  • SetWidgetPlanesLocked
  • SetWidgetPlanesRotationLocked
  • SetWidgetPlanesRotationLinked

Please check if problem still persists as soon as T27490 is merged into develop or directly with D329 (is open for review by the way ;)

Please regard changes of/for T27490.

Please check if problem still persists as soon as T27490 is merged into develop or directly with D329 (is open for review by the way ;)

Please check if problem still persists as soon as T27490 is merged into develop or directly with D329 (is open for review by the way ;)

@hettich Why? 🤔

New documentation has been reviewed by André, next step would be to have it reviewed by a non-MITK developer (MITK Workbench user). This could probably happen during a release phase / checklist session.

Thank you for your response and for pointing out the redundancy, I will fix this next week.

@kalali Your solution solved the problem. I'd like to point out that SetWidgetPlanesVisibility(true) is already called somewhere inside InitializeMultiWidget(), so just AddPlanesToDataStorage()is enough for rendering the planes.

Pushed new branch release/T27486-2020-06-19.

The error described above results from the function add seed that currently takes 3D images only. It can be solved with using a timeselector to crop the current time step and set a 3D seed.
However, the task is related to the discussion on time points versus time steps and should be revised accordingly.

I fixed the tutorial accordingly and close this task as resolved. If you still have problems, don't hesitate to reopen this task.

I can confirm that autocrop in the DataManager context menu is broken and that it probably was never adapted to the LabelSetImage data type: when someone autocrops a segmentation (which is a LabelSetImage since years now even for "binary" segmentations created by the old segmention view), the cropped image should also be a cropped LabelSetImage containing all labels and layers. Other crop strategies like crop to a certain label is subject of the Multilabel Segmentation View context menu, but not of the general DataManager context menu.

When the workbench is started from scratch it works.