The mitkSegmentationInterpolationController registers an observer on a segmentation image in order to get notified everytime the segmentation changes. This observer is never removed. Neither if the 2D interpolation is deactivated nor in the destructor or if the image is removed.
This is quiet annoying since even if interpolation is completely disabled MITK rescans the segmentation volume which is quiet time consuming.
New remote branch pushed: bug-14030-segmentationInterpolationControllerDoesNotRemoveObserver
[aba2ae]: Merge branch 'bug-14030-segmentationInterpolationControllerDoesNotRemo
2012-12-17 15:06:23 Andreas Fetzer [a49454]
Workaround for bad 2D interpolation performance
Since the mitkSegmentationInterpolationController add an observer to the binary image
each time the segmentation is modified the whole image volume is scanned by the controller.
Even if the 2D interpolation is deactivated.
Added a boolean to activate/deactivate 2D interpolation