The effect using the MxNMultiWidget

Deleted branch from rMITK MITK: bugfix/T29318-DeleteObsoleteResources.

Pushed new branch to rMITK MITK: bugfix/T29318-DeleteObsoleteResources.

Deleted branch from rMITK MITK: bugfix/T29318-SegmentationToolIconsAndCursors.

{D722} is a proposed change for checking the render window geometry and give the user a warning if the geometry is not aligned with the selected reference geometry.
The effect can be seen here:

I created a first working version, based on @s434n's branch (see above). I created an integration branch, made some changes and rebased everything to the latest develop.
Now the following changes, which are already merged into develop, are included, since the integration branch is based on e4d0b1591a17054b4c6792c235aa41345b842cb7:

• T27613: Improve reinit behavior / {D675}
• T26496: [mxn multi widget] Re-initializations reset all render windows / {D708}
• {T26627} / {D714}

Pushed new branch to rMITK MITK: bugfix/T29318-SegmentationToolIconsAndCursors.

Test the switch to TransferLabelContent. It makes it faster, but not fast enough for a good UX. I think the only scalable way is to only process the boundingbox region of the image that (potentialy) altered instead of always the whole image.

@isensee could you provide such a large image?
P.S.: not needed any more. found one.

Thank you 🙏

Here's the first batch of clean-up action. Needs to be continued!

In T24398#241998, @floca wrote:

Our side or also the CTK part.

Hm, lets put it as known issue and discuss its priority when we plan the spring release.

thank you for looking into that matter.