Deleted branch T24716-imageDataItem-limit-expanded.

Deleted branch T24332-update-SimpleITK-and-use-system-python3.

Deleted branch T23343-enable-microservice-based-reading-for-dicom-editor.

A couple of days after writing that, I found the code that is setting the initial state to visible.

In T27389#204198, @Oshio wrote:

@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.

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.

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 reproduce the error. There was a change in the StdMultiWidget so we have to adapt the tutorial. A specific initialization-method was added, so we need to call InitializeMultiWidget before accessing the render windows (which does some things for us so we can remove some lines from the tutorial).
The level window slider was removed from the StdMultiWidget and needs to be added additionally.

This issue is not wDB related, but MITK related:
Query with CGET activated and then Retrieve:
Retrieve does not work, MTIK directly shows:

This does still not work (Retrieve from wdB fails, when going throw the "Checkliste DICOM Browser".
I have to look into this.

You mean like

-Wno-error=catch-value=

Alright, thanks for your support!

Thanks for that. The problem arises from a insufficient implementation of the LabelSetImagIO. It currently ignores the time geometry and additional properties :(.

Sorry I did not mention this, but I use the multi label segmentation.

In T25939#173903, @full wrote:

For the sake of completeness: I did as you suggested and created a segmentation from scratch and exporting it as nrrd. This did not solve the problem.

Then there might be another bug involved. Could you make such a segmentaton (must not be a meaningfull) store it as nrrd and provide the stored NRRD?

Thank you for your extensive response.

The reason is (most certainly, but not verified!), that the nifti segmentations do not store correct timepoints for each frame. If loaded, they will get the default time geometry. (starting with 0 ms and a duration of 1 ms per frame). This is one of the problems I addressed last december with my camic info mail, to make people aware of current problems with using nifti (cf nrrd format) when storing data.

The tutorial ("Welcome screen") has light theme and the old icons. This might be quite confusing for new users.

warnings as errors on by default: New CMake option WARNINGS_NO_ERRORS

Is this really already resolved?

Pushed new branch T25186-version-number-update.

Pushed new branch T25191-v2018.04-beta-DICOMBrowser-ListRequests.

Known Issues:
Under Linux after compiling i have to start the program twice, the first time with --BlueBerry.clean. I use this script to compile and start it faster:
#!/bin/bash