Page MenuHomePhabricator

Pixel value on the status bar with segmentation
Closed, ResolvedPublic

Description

If an image and a segmentation is made visible then the pixel value displayed on the status bar is from the segmentation, not from the base image. This is independent of which image is selected.

This is a little bothering, since if you want to see a pixel value in a ROI than you have hide the ROI first. If the ROI is checked on, you see 1 or 0 on the status bar.

I note that the statusbar is updated from two places in MITK, and both are active. *QmitkStdMultiWidget and mitkSliceNavigatorController if I remember well.) So if this will be fixed, it has to be fixed in both places, or to remove one of them.

Event Timeline

Changed Target Milestone to upcoming release

Updating target milestone to upcoming release

New remote branch pushed: bug-10488-PixelValueOnStatusBarWithSegmentation

Fixed in HandleCrosshairPositionEventDelayed() in QmitkStdMultiWidget wich is called after mitkSliceNavigatorController. Now if you click on a binary image it searches for source images of the binary image. If there is a source image the image information of the source image will be displayed in the status bar otherwise the image information of the binary image will be displayed.

I would suggest to open another bug for mitkSliceNavigationController and disable the execution of the event if QmitkStdMultiWidget is in use and HandleCrosshairPositionEventDelayed consumes the crosshair event already.

New remote branch pushed: bug-10488-PixelValueOnStatusBarWithSegmentationRebased

Yep I totally agree with you. The duplicate code in the QmitkStdMultiWidget and the SliceNavigationController is not nice, especially the duplicate execution of this code. Because of the latter: Could you please add the binary image stuff to the SliceNavigationController as well? Currently since the SliceNavigationController is setting the status bar text either the displayed pixel value is constantly switching between the binary value and the image's value.

Ok I added the binary image stuff to SliceNavigationController as well and pushed it onto remote branch.

Could you please add your manual testing description to the application checklist? You could ask Andreas for help if necessary.

The testing description is added to the list. In my oppinion it's sufficiant to test the whole szenario.

[443b01]: Merge branch 'bug-10488-PixelValueOnStatusBarWithSegmentationRebased'

Merged commits:

2013-04-15 12:59:11 Michael Bauer [9b56fa]
Implemented new method GetTopLayerNode to calculate the highest layer image in the
DataStorage which isn't a helper object and returns it. This method is used in ExecuteAction.

Adjusted the way to display status text in ExecuteAction.
Now the behavior of displaying is the same as in QmitkStdMultiWidget.


2013-03-25 16:20:37 Michael Bauer [b7bd1f]
Adjusted logic in HandleCrosshairPositionEventDelayed().
Now if you click on a binary image it searches for source images of the binary image.
If there is a source image the image information of the source image will be displayed in the status bar otherwise
the image information of the binary image will be displayed.


2013-02-13 18:03:00 Michael Bauer [5bb24a]
Added new method for layer computation.
Added some code to prevent the StatusBar from displaying image information
of a binary image if the binary source image is available.
In case that the source image is available the status bar will display the
pixel values of the source image.
You will see the binary image on top of the source image but the pixel values
of the source image in the StatusBar.


2013-01-23 17:41:56 Justin Iszatt [98e61d]
Started working on the bug. look at the qmitkstdmultiwidget at line 1626