Hi,
one solution would be to move the code that switches between the display
interaction configurations from mitk::ToolManager::ActivatTool(int) to
mitk::Tool::Activated() and mitk::Tool::Deactivated(), respectively. In
this case the implementations could override the default behaviour.
The other solution could be just simply remove that code, and let the
concrete Tool implementations handle this.
What do you think?
I like that now the different tools can reinterpret different set of mouse
events.
Regards,
Miklos
------------------------------------------------------------------------------
Own the Future-Intel(R) Level Up Game Demo Contest 2013
Rise to greatness in Intel's independent game demo contest. Compete
for recognition, cash, and the chance to get your game on Steam.
$5K grand prize plus 10 genre and skill prizes. Submit your demo
by 6/6/13. http://altfarm.mediaplex.com/ad/ck/12124-176961-30367-2
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
