| wegner | |
| Nov 12 2010, 3:28 PM |
| F634: 6047_patchNodeDependentPointSetInteractor.patch | |
| Nov 12 2010, 3:31 PM |
Add a feature to let a PointSetInteractor be dependent on one data node.
Example situation:
Landmark Registration: Two different images, each shown in its own renderwindow (render specific properties), but both stored in the same data storage. Also added to data storage: two PointSets and PointSetInteractors each to be assosiated to one image.
Only the PointSetInteractor associated to the shown image shall add points to the PointSet.
I have created a new class as described in Wiki specification page.
StateMachine.xml had to be adapted to enter Mode_Deactivated in state machine once a point has been added. Otherwise the one statemachine will be kept as selected state machine in GlobalInteraction and it will reveive the next event without asking CanHandleEvent. Yet only pattern pontsetinteractor has been adapted. Other patterns need to be adapted too to be used with NodeDependentPointSetInteractor.
A change in the process of selecting state machine shall be done in the future to remove modes Mode_Selected, Mode_Subselected and Mode_Deselected because they were mainly be ment to be for hirarchical interaction (didn't work out!).
[SVN revision 29824]
ADD (#6047): Adding interactor that is dependent on a property of an associated data node. Also adding test and minor format changes of StateMachine.xml