Placeholder for external project updates, minimum CMake version, and Qt version

I went through all Noteworthy tasks of the list above and summarized the ones were I was assigned (we should split it later into API changes and other noteworthy features):

Pushed new branch T26721-UpgradeQtVersion.

Noteworthy as it containes BREAKING CHANGES for some ModelFit dependent modules and plugins.

A current blocker for use of NAKO data, therefore set as high priority.

Priority high for all plugins that are part of the release (see table above).

I think I found a nice solution. Depth peeling is set per renderer, not for the whole application. So it makes sense to activate it only for 3d renders. Side effect: probably speeds up rendering a little bit.

Blocked by the fact that e071-jenkins is not yet reachable from outside.

I am sorry for being late reply.

Testing is postponed/moved into T27481. Waiting for test data that can be put into mitk-data.git.

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.

In T27477#203973, @thomass wrote:

I used a master that was three weeks old, I will double check on the current develop

I used a master that was three weeks old, I will double check on the current develop

@thomass Have you used a current build of develop. Currently, if not set by the user in the preferences, it always selects the first tab. "Favorite node list" is never the first tab in the dialog, because the special dialogs (favorite and history) are always added last.

This is also already on the TODO list of the packaging rewrite.

@nolden https://github.com/NVIDIA/ai-assisted-annotation-client/issues/57

I am re-opening this since I think this will also become more relevant with the foreseeable use of other REST APIs from MITK , e.g. how did the nvidia segmentation tool resolve this issue for the windows installer? @kislinsk could you comment?

T23741 introduced the useage of boost::uuid as internal implementation of UIDGenerator.

In T23741#203910, @kalali wrote:

Can T14333: Improve mitk::UIDGenerator be closed?

It's depth peeling and it is not solved with VTK 9. I tried to narrow down the issue in a minimum VTK application but I wasn't able to reproduce it. As quite a significant amount of time already was spent here, I will probably reintroduce preferences to disable/enable depth peeling and declare this issue as a known issue.

Fixed a bug where images appeared brighter as they should as soon as the 3d renderer rendered its first image. Only thing missing now is ACVD I guess.

We could add a check in QmitkSlicesInterpolator::SetCurrentContourListID()

A static mask is generated in QmitkSegmentationView::CreateNewSegmentation() with

const auto refTimeGeometry = image->GetTimeGeometry();
auto newTimeGeometry = mitk::ProportionalTimeGeometry::New();
newTimeGeometry->SetFirstTimePoint(refTimeGeometry->GetMinimumTimePoint());
newTimeGeometry->SetStepDuration(refTimeGeometry->GetMaximumTimePoint() - refTimeGeometry->GetMinimumTimePoint());

mitk::ProportionalTimeGeometry::GetGeometryForTimeStep returns nullptr during
mitk::Vector3D spacing = workingNode->GetData()->GetGeometry(time_position)->GetSpacing() inside QmitkSlicesInterpolator::SetCurrentContourListID().
Obviously because IsValidTimeStep(timeStep)) for e.g. timestep = 2 is false.