Bug(s) in CTK:

If you ask for all the nodes from data storage then you get also child nodes in random order. In the previous implementation, visibility of all child nodes of widgets are set to True when the widgets node is reached. Nonetheless, child nodes visibility were afterwards set to False in the outer loop.
Now the loop is only done on nodes in the first level that contain data, therefore crosshair nodes stay always visible.

Could you elaborate on this? I don't get it: aren't we processing each single data node inside the data storage?

In Ubuntu 18.04 data storage is accessed in random order therefore the visibility of crosshair was set randomly. Fixed in branch: T19683-ShowOnlySelectedNodesCrosshairVisibility-RandomAccess.

Pushed new branch T19683-ShowOnlySelectedNodesCrosshairVisibility-RandomAccess.

Hm, ok. Then the log output is somehow inconsistent, with what is loaded into the workbench.
@kislinsk How do one enforces the more detailed log? The logging console is capable to show more information then given in the attached log.

As the download step is actually a git clone step the patch command is executed everytime instead of only. The patch command will return a non-zero exit code for already applied patches which probably causes the error.

Pushed new branch T26556-Python3.6-macOS.

Pushed new branch T26277-PhantomBasedUSCalibration-Integration.

This is actually a huge topic with many implications. So we will defer the discussion.

cpprestsdk compiles fine but when triggered from superbuild the Debug configuration fails with an unspecified error.

Pushed new branch T26554-OpenMP.

Great, now websocketpp is incompatible to Boost 1.70.

Pushed new branch T26546-UpgradeBoostToVersion1.70.

This will further allow to remove the string query (e.g. "axial") for render windows but allow a type-based request.

Only one file in the stack was chosen on both cases.

In T26451#184491, @jsolislemus wrote:

(1) Using the Open File button -> Selected the (autoselect) -> NOT clicking on "apply the same to the remaining files" (file MitkWorkbench_MRIreadeAutoselect.log and looking as in the screenshot attached). The images were loaded individually, and not as a single dicom.

Regarding this workflow: I have another question. How many files did you select in the dialoge? One file of the stack as selection would be sufficient.

mitkBaseRenderer.h already contains the enum for Standard2D and Standard3D, which is needed if one wants to switch between 2D and 3D view.
The file is part of MITK Core so that could be a good location to put the view direction enum.

Also fixed a few other compiler errors on macOS and improved handling of the OpenMP dependency.

Pushed new branch T26544-GuardTestSettings.

Please set a priority other than Needs Triage for tasks as it clutters our triage queue otherwise.

Pushed new branch T26540-FixWarningAsErrorInUltrasoundTrackingNavigation.

Hello, sure. Please let me know if you need clarification, I am writing this with some haste, so I might not be as thorough or clear in my explanations.

@jsolislemus Thanks for the info. If I understood it correctly also the official installer shows this problem. Could you please do me a favor and check with the official installer if you have the same loading problem, if you do not use the DICOM browser, but instead the normal file open dialog or dragNdrop. With this information we can narrow it down a bit more.
Thanks.