Change Details

Currently the UpdateStatusBar method in `QmitkImageNavigatorView` and in `mitkDisplayInteractor` duplicate a lot of business logic. The part of the function that extracts the pixel value from the image and updates the statusbar is the same. The redundant part should be extracted and be put in one function that can be called by both (`QmitkImageNavigatorView::UpdateStatusBar()` and `mitkDisplayInteractor::UpdateStatusBar()`. Similar code is also used inside `StdMultiWidget::HandleCrosshairPositionEventDelayed`, where the image / pixel information is extracted and passed onto `mitkStatusBar`.

Currently the UpdateStatusBar method in `QmitkImageNavigatorView` and in ~~`mitkDisplayInteractor`~~ `mitkDisplayActionEventBroadcast` duplicate a lot of business logic. The part of the function that extracts the pixel value from the image and updates the statusbar is the same. The redundant part should be extracted and be put in one function that can be called by both (`QmitkImageNavigatorView::UpdateStatusBar()` and ~~`mitkDisplayInteractor::UpdateStatusBar()`~~ `mitkDisplayActionEventBroadcast::UpdateStatusBar()`. Similar code is also used inside `StdMultiWidget::HandleCrosshairPositionEventDelayed`, where the image / pixel information is extracted and passed onto `mitkStatusBar`.

Currently the UpdateStatusBar method in `QmitkImageNavigatorView` and in ~~`mitkDisplayInteractor`ractor`~~ `mitkDisplayActionEventBroadcast` duplicate a lot of business logic. The part of the function that extracts the pixel value from the image and updates the statusbar is the same. The redundant part should be extracted and be put in one function that can be called by both (`QmitkImageNavigatorView::UpdateStatusBar()` and ~~`mitkDisplayInteractorteractor::UpdateStatusBar()`~~ `mitkDisplayActionEventBroadcast::UpdateStatusBar()`. Similar code is also used inside `StdMultiWidget::HandleCrosshairPositionEventDelayed`, where the image / pixel information is extracted and passed onto `mitkStatusBar`.