Page MenuHomePhabricator

[mxn multi widget] Pixel value view does not change on crosshair selection
Closed, ResolvedPublic

Description

The newly introduced pixel value view does not react on the crosshair change inside the mxnMultiWidget.

This is due to the use of the QmitkSliceNavigationListener which only reacts if the corresponding slice navigation controller of the render window, where the user has clicked into, has changed. However, for the mxnMultiWidget widget the slice navigation controller did not change since the slice did not change on a crosshair selection change. Only the two other coordinates for the crosshair planes changed but the view stayed on the same 2D slice / plane.

(In the StdMultiWidget case the two "orthogonal" planes and their slice navigation controllers (rather their slice steppers) changed and thus the GeometrySliceEvent was sent).

Revisions and Commits

rMITK MITK
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision
Restricted Differential Revision

Event Timeline

kalali renamed this task from [mxn to [mxn multi widget] Pixel value view does not change on crosshair selection.Thu, Nov 10, 6:09 PM
kalali triaged this task as Normal priority.
kalali created this task.
kalali updated the task description. (Show Details)
kalali added a subscriber: s434n.
kalali added a revision: Restricted Differential Revision.Fri, Nov 11, 6:58 PM
kalali moved this task from Backlog to In candidates on the MITK (v2023.04) board.

Render window specific visibility has to be covered, as mentioned in D756#26848. This will be done in T29403: [mxn multi widget] Concept for crosshair data type.