Page MenuHomePhabricator

Use QmitkAbstractView as the super-class for QmitkSegmentationView
Closed, WontfixPublic

Description

We should use the new super-class QmitkAbstractView. It provides better life-cycle, selection, and render window support.

I started the port and it is *mostly* working, but there are still bugs and a few places where we need to think about a proper solution.

Using the new super-class was actually straight-forward, but trying make the view independent of the QmitkStdMultiWidget posed some problems.

The current bug-branch compiles and segmenting works sometimes...

Event Timeline

zelzer added a subscriber: zelzer.

The branch is available here:

bug-12844-use-qmitkabstractview-in-segmentation-view

I added "TODO" comments in QmitkSegmentationView.cpp and QmitkSlicesInterpolator.cpp where things were not clear to me.

Generally, I tried to use only a list of mitk::SliceNavigationController instances in QmitkSlicesInterpolator to be QmitkStdMultiWidget independent. Mostly, they replace the "dimension" integer.

Segmenting right now only works if the user did not click in any of the render windows before activating a segmentation tool.

Also, the application crashes if the segmentation view is visible on start-up and the app is closed immediately (some itk observers do not exist anymore).

New remote branch pushed: bug-12844-use-qmitkabstractview-in-segmentation-view-instead-qmitkfunctionality

This bug could not be fixed for release 2013-06. Setting target milestone to next release

Current release is finished. Reseting target milestone...

kislinsk added a subscriber: kislinsk.
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.