If you create e.g. a 3D interpolation based volume segmentation and activate the rotation or deformation operator, the plane will not be deselected if the cursor leaves the rendering window at the right border. The user is then prevented from interacting with the rendering window, e.g. zooming and rotating. Additionally, if you leave the window as described while the deformation operator being activated and then deactivate the deformation operator, the plane will be permanently selected. Thus, the user interaction will be blocked. Same does not apply for the rotation operator.
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | None | T13037 The rendering interaction freezes after deformation operations. | ||
Resolved | None | T14492 Migration of AffineInteractor3D and SurfaceDeformationInteractor to new Interaction Concept |
Event Timeline
The problem occurs because the AffineInteractor3D and the SurfaceDeformationInteractor3D doesn't know that the mouse is outside the 3D render window. They only change the color of the surface based on the display position event of the mouse (over the surface or not). When the cursor is outside the 3d render window, the interactors doesn't get any event, so the color remains the same.
Proposed Solution:
Using the existing leaveEvent from Qt (QEvent) and adapting this to a mitkEvent.
Should be discussed with the group.
With the new interaction concept the interactors should receive more event types (qt,...) and can handle these. The bug will be fixed after the merge of the interaction project from Christian.
This bug could not be fixed for release 2013-06. Setting target milestone to next release
What is the status of this bug? Apparently there is a fix available? We should try to include it into the upcoming release.
This bug was not fixed within in the release 2013.12 but should be fixed within the next release