Change Details

Applications can crash because of a bug in `mitk::PlaneGeometry` and `mitk::SlicedGeometry`. The crash happens when reinitialising the renderers along a given orientation (sagittal, coronal or axial). The crash happens because an invalid transformation matrix is created during the initialisation. This is because of the code I added to determine which axes is closest to the individual world orientations. In extreme cases when the volume is rotated exactly by 45 degrees, the same axis will be assigned to different orientations, and to some other orientations no axis will be assigned. It is probably not common to have images which are rotated exactly by 45 degrees around some world axes. We discovered this because we have an affine transformation plugin that allows the user to apply any transformation on a volume interactively. I will send a PR shortly.

Applications can crash because of a bug in `mitk::PlaneGeometry` and `mitk::SlicedGeometry`. The crash happens when reinitialising the renderers along a given orientation (sagittal, coronal or axial). The crash happens because an invalid transformation matrix is created during the initialisation. This is because of the code I added to determine which axes is closest to the individual world orientations. In extreme cases when the volume is rotated exactly by 45 degrees, the same axis will be mapped to different orientations, and some axis will not be mapped to any orientations. It is probably not common to have images which are rotated exactly by 45 degrees around some world axes. We discovered this because we have an affine transformation plugin that allows the user to apply any transformation on a volume interactively. I will send a PR shortly.

Applications can crash because of a bug in `mitk::PlaneGeometry` and `mitk::SlicedGeometry`. The crash happens when reinitialising the renderers along a given orientation (sagittal, coronal or axial). The crash happens because an invalid transformation matrix is created during the initialisation. This is because of the code I added to determine which axes is closest to the individual world orientations. In extreme cases when the volume is rotated exactly by 45 degrees, the same axis will be assignmapped to different orientations, and to some other orientations no axis will be assignedsome axis will not be mapped to any orientations. It is probably not common to have images which are rotated exactly by 45 degrees around some world axes. We discovered this because we have an affine transformation plugin that allows the user to apply any transformation on a volume interactively. I will send a PR shortly.