Pushed new branch T26434-ArcanistBaseCommitRule.

Pushed new branch T26431-compilation-fixes-gcc9-clang8.

VTK has a little bug in vtkShader.cxx around line 76: GLuint handle = glCreateShader(type);. The handle is not tested against 0 which leads into a misleading error message like above. The actual problem is that vertex and fragment shaders can be created (and compiled successfully) but not geometry shaders.

In T26427#182768, @kislinsk wrote:

Our example steps do not work, they start however. Render window is just black.

Also experimented with environment variable QT_OPENGL=software and QT_OPENGL=angle. VTK's GLEW is already unable to initialize with these settings.

Our example steps do not work, they start however. Render window is just black.

Pushed new branch T26413-Nifti2.

Potential conflicts: Multiple render windws, Qt resp. shared OpenGL context with Qt.

I tried the VTK MarbleShader example and it works.

Tried every combination of options but it's always the same error:

Important for T26144 (and also open office virtual desktops).

64bit builds of Mesa 3D for Windows: https://github.com/pal1000/mesa-dist-win/releases

Added ITK example to project template.

Pushed new branch T26426-EPCustomization.

Pushed new branch T26424-FixTests.

Works with NSIS 2.51.

@neher Please base the fix on the releases/2018-04 branch.

The ChangedNodeEvent of the data storage is not used inside the QmitkDataStorageComboBox. A reason for this might be that the changed node event is sent very often.
Instead, a specific listener for the name property is used in QmitkDataStorageComboBox::InsertNode.

Pushed new branch T26372-AddNavigationDataXMLtoCSVFeature.

This branch was merged into the master recently. @mittmann Can we close the bug?

It turned out that if I load the file holding the segmentation alone and the right click -> convert to segmentation, everything works as expected. Only if I load the raw image plus the corresponding segmentation simultaneously (which is my usual workflow), the bug above arises.

Alright, thanks!

HI Peter, MITK (2018-04-4) the the current milestone. I nearly missed this task as you put it in the already archived milestone MITK (2018-04). The safest way to raise awareness is to just set the task priority to Needs Triage and stick with the MITK tag. ❤