We added some code to identify two cases:

1. Non-aligned image geometry
2. View and image are not aligned after cross hair rotation

I see your point, however right now we can't come up with a clean solution so that 2D handles make sense if the axes are not aligned.
One possible solution could be to enforce a reinit like it is currently done in the segmentation plugin.

Non-axis aligned images should give a warning that you need to reinit them first. The problem is that handles for

• non-axis aligned images
• images in which you rotate the crosshair

Seems to be very odd, since the coronal view is not at the crosshair position anymore but somewhere completely different.
@kislinsk is this somehow related to the image slicer issues?

It seems that it is somehow dependent on the data whether the handles work or not.
Just today I run into the same problem so you were a bit faster ;) I will have a look.

Switching off interpolation leads to more accurate results but on the contrary produces some weird artefacts which cannot be quite explained yet.

Pushed new branch T24172-InterpolationForSmoothedPolygonModel.

Creating smoothed polygons now works for segmentation and multilabel without causing any crashes. However, no multilabel support is provided yet. The next step will be to cover multilabel support in QmitkCreatePolygonModelAction or rethink the structure as such (i.e. why we can't create a surface without segmentation or why the action is triggered randomly).
Furthermore, we removed ShowSegmentationAsSmoothedSurface from both, segmentation and multilabel. We have to further investigate why the class was created in first place and if there is any advantage of the ITK implementation used in this class as opposed to the VTK driven implementation in mitkManualSegmentationToSurfaceFilter.

Pushed new branch T23078-FixCrashOfOnCreatingSmoothedPolygonSurface.

On some Windows systems it only crashes if plugin multilabel is switched on & open or no plugin is open.
If plugin segmentation is open it works fine. On Linux it even happens if the segmentation plugin is open.

Pushed new branch T22935-MinorFixesOfCompileErrorsCausedByITKUpgrade.

Pushed new branch T22620-RegionGrowerInHighIntensityRegions.

Use a duplicate of the segmentation image to determine the smoothing criterion. Otherwise, the initial seedpoint can be erased in the smoothing operation.

Pushed new branch T22421-ImageCropperCropsWrongTimeStep.

Pushed new branch T22396-ImageCropperRenderUpdateScrolling.

I guess @hettich is the expert when talking about the whole orientation issue. After determining correct axes definitions (which seems to be the hardest part), the visualization should be fairly easy using @kolbch's new concept.

Pushed new branch T22247-ImageCropperHandleColorDisappeared.

Pushed new branch T22123-Add-correct-documentation-level.

Pushed new branch T19984-ImageCropperIntegrationBranch.

Pushed new branch T19984-ImageCropperIntegration.

Correction Tool crash

Segmentation Result after using Fill

Actual Behaviour
While being in crosshair rotation mode, pressing another second button causes the interactor to remain in that previous state and the cursor icon to freeze.