Status:

1. Currently some tools (FastMarching, LiveWire and Picking) listen to time step changes via there UI class (QmitkFastMarchingTool3DGUI) which uses a QmitkStepperAdapter in conjunction with GetSliceNavigationController()->GetTime().
2. Last week (without being aware of #1) searching for a suitable place to communicate changes of time we thought it might sense to add a mitk::Message<> SelectedTimePointChanged to the toolmanager (as it allready offers ActiveToolChanged, ReferenceDataChanged, WorkingDataChanged, RoiDataChanged). So tools can register at the toolmanager if they want to now it current time has changed.

I am open to any solution. But we should have only one.

Additional thoughts:

• Even if we stay with #1, we have to rework the tools, as solely listen to time step is not enough. The current time point is important to correctly navigate.
• With #2 time awareness of tools would not depend on the UI implementation and Qt.
• With #2 time awareness of tools would depend on the toolmanager and can not be altered by the tool (do we need such a possibility?)
• Is mitk::message a concept we can still use? (at least it is still used in the toolmanager)

Any opinions or insights?