Pushed new branch release/T27910-2020-Week-43.

Slashes are now replaced by underscores.

Deleted branch bugfix/T27902-ReplaceSlashesInInstallerName.

Pushed new branch bugfix/T27902-ReplaceSlashesInInstallerName.

This tasks came up again in the discussion of the clipping plane plugin, which allows for volume annotations for segmentations. Since we decided to remove the clipping plane plugin from the MITK release, this task was tagged with "Next Milestone" in order to restore the useful feature of volume annotations also outside the clipping plane plugin.

Deleted branch bugfix/T27851-FixLabelSetPresetsAndMakeThemMoreAccessible.

Two options in order to integrate Epiphan were discussed:

Deleted branch feature/T27789-ClippingPlanePlugin.

Pushed new branch feature/T27789-ClippingPlanePlugin.

In T26382 the recent developments are summarized.

Flags to check whether the "Next" button has being activated have been added. Needs to be adapted due to a bug:

I got this error message on SS FSE CEST, ERROR: Image(0000027E06632400): A spacing of 0 is not allowed: Spacing is [0.31, 0.31, 0]

Ups ;) Replace with - or _?

Also, in the zip folder for example, we suddenly have nested folders: MITK-snapshots/2020-09-25-123-gabcdefab-windows-x86_64.

Deleted branch bugfix/T27900-TypoInReference.

Pushed new branch bugfix/T27900-TypoInReference.

This notification can be omitted, since there is already a "generating report" notification on the background.

Agree, but we should definitely package Python instead of relying on system python in any case as there are more strings attached. Even between minor Python updates there are imcompatibilities especially when SWIG is involved. Also we rely on certain Python packages like numpy or SimpleITK. So the plan is:

I was just about to add a note that there is the general question how to handle python in installers. I guess for just having the basic runtime available it would be ok to just load libpython3.so or libpython3.8.so and let the system take the right one from the right path. But on Windows I guess most people don't install Python in system locations. Anyway I think this could be fixed even with the current packaging if we need it for 2020, but I'm just reporting, no pressure from my side ;)

I guess this is not specific to Fedora (not even to Linux) as we do not yet package python into the installer as far as I know. As this task is a bit moe vorbose than T26258: MITK and python only works with the specific python version the installer was created with, I will close the other one as duplicate.

• I renamed the context menu entries to Load/Save LabelSet Preset
• I made these actions also available as tool buttons in the Multilabel Segmentation View
• I fixed quite a few bugs in the loading mechanism
  • Existing label properties are now overridden by a preset
  • Layers/labels in other layers work now
  • The state of the Multilabel Segmentation View is now updated after a preset was loaded

Pushed new branch bugfix/T27851-FixLabelSetPresetsAndMakeThemMoreAccessible.

Deleted branch hotfix/T27887-fix-packaging-with-system-qt.

Pushed new branch hotfix/T27887-fix-packaging-with-system-qt.

stabilityByAlgorithmStacked is now replaced by stabilityByAlgorithm(....., stacked=TRUE)

The functionality is already in a separate class LabelSetIOHelper so it is not restricted to DataManager actions per se. The code in these actions is of pretty bad quality, though. The first step will be to clean up these actions. I will also rename the actions in the context menu to Load LabelSet Preset and Save LabelSet Preset to make them more distinguishable. Then I will look into the view to see if the functionality is already there somewhere or if we must add it. I also already noticed that while the preset files contain information about layers as well, only the labels of the first layer are loaded.

I'm all in for that. We already discussed that we will focus again on this task {T26754} and its subtasks. This also includes

Automatic GUI testing

and

move as much tests as possible to Unit-Tests