Pushed new branch T26721-Qt-5.12-Fix.

Created a PR with the fix https://github.com/MITK/MITK/pull/241

Pushed new branch T26761-msot_mcx.

Pushed new branch T26760-noise_model.

on MITK master:

I just tried to use CTest with a branch. This is not working when I use set(GIT_BRANCH "Txxx"). I assume this is because this makes the script use the raw Phabricator file, which is not working, according to the task name.
However, since branches are not mirrored to GitHub, the proposed solution is not an option for me? Or is this not related?

Status as of now:

Pushed new branch T26721-Qt-5.12.

For now we should stick with the Qt 5.12 LTS, as long as 5.13 does not work reliably (see Windows issue above). We can add a CMake warning/error for now that does not allow to proceed configuring MITK with Qt > 5.12.

Look at your nightlies. This is the fix. You're the only one allowed to merge into the master branch of MITK-Diffusion.

?

@neher : Is this resolved?

Is this resolved with 4cda20fc6a60? The buttons were removed but do we want to have them with the correct logic (@kislinsk)

Ok, just created https://github.com/MITK/MITK/pull/240

Pushed new branch T23293-nullptr.

@neher, you probably want to merge this. :-)

Pushed new branch T26756-mitkFunctionCreateBlueBerryApplication.

I tried the idea described above today and it fixes the behavior of my interactor that uses the mouse wheel in a 3D window. With this patch the MITK interactor gets to see the event first and can decide whether or not is is handled.

Pushed new branch T23293-override-Oct2019.

Revive task.

Pushed new branch T26752-Boost-RPATH.

Pushed new branch T26747-AppleClang-Errors.

Actually, @hempe informed me that the render window menu is not flickering anymore in the latest stable release (if you mean with flickering: not being able to use the render window until you click inside the render window to set its focus).
I wanted to take a look into the diff this week.

@hempe @kalali Maybe related to the flickering render window menu issues?

That's a strong indicator that your graphics H/W causes trouble with the "modern" OpenGL version that VTK 8.x requires. I'm open for new ideas but I think this is something that is not fixable other than trying newer drivers or more recent H/W. In theory, everything not older than 6-7years should work with OpenGL 3.2, but as it turned out, there's a lot of fake-compatibility in older drivers.

In T26736#187698, @kislinsk wrote:

You can also test an MITK 2016.11 installer as the requirement of a newer OpenGL version was introduced in MITK 2018.04 with VTK 8.x.

I tested with Ubuntu 16.04 in VM and also on a Ubuntu 18.04 host. Nvidia graphics.

Thank you for your efforts. I completely understand your decision with regards to Ubuntu as the main Linux platform. When I have time I'll try to start MITK from an Ubuntu live CD on this machine and report my findings here. One remark: if the issue in MITK is due to an issue with an upstream version of MITK dependencies (or system libraries), then we might encounter this issue in future versions of Ubuntu.

Works for me on various Ubuntu machines and Windows.

Firstly, thank you very much for the detailed and complete bug report. It really is a pleasure to have all information without asking for every detail.

The current status of this task is documented by the Bachelor's thesis of @jungsi.