Change Details

While placing a line or any other planar figure using the QmitkMeasurementView the method DisableCrosshairNavigation() is called. However, when trying to get the DisplayInteractor using 'auto displayInteractor = dynamic_cast<mitk::DisplayInteractor*>(us::GetModuleContext()->GetService<mitk::InteractionEventObserver>(eventObserver));' a nullptr is always returned, and the "DisplayConfigMITKLimited" is never set.

While placing a line or any other planar figure using the QmitkMeasurementView the method DisableCrosshairNavigation() is called. However, when trying to get the DisplayInteractor using 'auto displayInteractor = dynamic_cast<mitk::DisplayInteractor*>(us::GetModuleContext()->GetService<mitk::InteractionEventObserver>(eventObserver));' a nullptr is always returned, and the "DisplayConfigMITKLimited" is never set. (IMPORTANT) **API-breaking changes** The `DisplayConfigPACSBase.xml` has been changed such that the `alwaysReact` parameter is now set to false (`<param name="alwaysReact" value="false"/>`). This will change (and possibly break) expected behavior when using this display interaction configuration in conjunction with a data interactor (e.g. `PlanarFigureInteractor`: A specific mouse event will now only be handled by the data interactor and not be forwarded to the display interactor. This is now in line with MITK-interaction configuration files, where the parameter was already set to false before.

While placing a line or any other planar figure using the QmitkMeasurementView the method DisableCrosshairNavigation() is called. However, when trying to get the DisplayInteractor using 'auto displayInteractor = dynamic_cast<mitk::DisplayInteractor*>(us::GetModuleContext()->GetService<mitk::InteractionEventObserver>(eventObserver));' a nullptr is always returned, and the "DisplayConfigMITKLimited" is never set. (IMPORTANT) **API-breaking changes** The `DisplayConfigPACSBase.xml` has been changed such that the `alwaysReact` parameter is now set to false (`<param name="alwaysReact" value="false"/>`). This will change (and possibly break) expected behavior when using this display interaction configuration in conjunction with a data interactor (e.g. `PlanarFigureInteractor`: A specific mouse event will now only be handled by the data interactor and not be forwarded to the display interactor. This is now in line with MITK-interaction configuration files, where the parameter was already set to false before.