2021 Week 12 (Late March)
The following - possibly updated - changelog can be viewed as formatted
article at https://phabricator.mitk.org/w/mitk/changelog/2021.12/.
🛠 Third-party dependency changes
We didn't upgrade any dependencies but added another patch for ITK v4.13.3 to make MITK compatible with the latest version of Visual Studio 2019.
✨ New features
- Made MITK compatible to the latest version of Visual Studio 2019
- Allow coupling of segmentation images to their patient images even if there is a numerically significant difference in their geometry information that still can be considered neglectable in the ordinary magnitude of units in medical imaging
🐛 Bugfixes
- Fixed compiler/linker error regarding the lrintf intrinsic in ITK's OpenJPEG third-party module for the latest version of Visual Studio 2019
- Fixed deferred update when toggling segmentation label visibility for labels in certain layers
- Fixed crashes in a few plugins that happened when a render window editor was not set as active/foreground editor
- Fixed segmentation previews for foreground values ≤ 1
- Reset segmentation color to the current color instead of the default red color when aborting the color chooser dialog for new segmentations
- Reset camera to initial position and orientation after taking 3-d multi-planar screenshots with the Screenshot Maker
- Skip corrupt properties during deserialization instead of adding null pointer properties
🔥 API-breaking changes
mitk::ContourModelUtils::FillSliceInSlice()
Foreground detection was hard coded to 1 < foreground. This was OK so far, since the foreground value was 255, but is problematic for general usage. The check was changed to fillForegroundThreshold <= foreground. The default of fillForegroundThreshold is 1 now.
Migration
It is highly unlikely that you are affected by this change. You only have to migrate if values of 1 are still considered background in your own segmentation tool. Pass a fitting fillForegroundThreshold parameter in that case. See D472 for more details.
mitk::NodePredicate[Sub]Geometry::GetCheckPrecision()
The GetCheckPrecision() method and the related NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_PRECISION constant were removed.
The equality functions of geometries do support coordinate precision and direction precision. This feature was not used by the predicates so far. It is needed to allow the predicates to be less pedantic with differences in coordinate comparisons, though. These tiny differences commonly occur in real world data when decimal places of numbers were cut off during serialization, but have no practical impact for the ordinary magnitude of units in medical imaging.
Migration
- GetCheckPrecision(): Use GetCheckCoordinatePrecision() or GetCheckDirectionPrecision() instead
- NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_PRECISION: Use NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_COORDINATE_PRECISION or NODE_PREDICATE_GEOMETRY_DEFAULT_CHECK_DIRECTION_PRECISION instead