SegmentationController will handle all results of the segmentation tools. The controller will accept both mitkImages as well as mitkContourModels and forwards them to the according service.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Duplicate | None | T16497 Data type for Segmentation | ||
| Wontfix | • schroedt | T16004 Implement a controller for Segmentation module. | ||
| Resolved | None | T16687 Tool tests using Interaction Testing Framework | ||
| Resolved | None | T16871 Interaction Testing Framework | ||
| Resolved | None | T16212 Let SegmentationController handle reference and working image |
Event Timeline
Comment Actions
Controller class is responsible for handling the result of segmentation tools and also the working and the reference image. So far only AcceptSegmetation methods have been implemented. All methods from SegTool2D were extracted and marked as deprecated. The handling of the image has been moved to T16212
A provider class ensures a single instance of SegmentationController for the segmentation plugin.
Comment Actions
Reopen bug.
Controller is not working as intended.
Storing of contours has been moved to segmentation data type so AcceptSegmentation methods of SegmentationController have to be redesigned.
Comment Actions
Controller handles segmentation image data (reference and working image). ToolManager gets a controller as member and passes all image requests to controller object. Thus the application can use several different ToolManager and SegmentationController instances at the same time.
Comment Actions
User schroedt has pushed new remote branch:
bug-16004-SegmentationController-integrate-Tool-interaction-changes
Comment Actions
This task was automatically closed because it wasn't updated at least since July 2016 (over 2 years). Please re-open this task if you think that it is still relevant. This most probably means that you will resolve it.