Hi Everyone, This may also be relevant to this debate: http://bugs.mitk.org/show_bug.cgi?id=10963
I think that for more general usage, the user needs to be able to register potentially any list of interactors with the QmitkStdMultiWidget. At the moment the QmitkStdMultiWidgetEditor contains QmitkMouseModeSwitcher, which gets connected to the QmitkStdMultiWidget which contains a mitk::MouseModeSwitcher. However the mitk::MouseModeSwitcher contains an enum InteractionScheme with only 2 modes, and a specific MouseMode, which is only valid for one of those InteractionScheme modes. I think it could be done nicely with a Chain of Responsibility pattern. Basically the MouseModeSwitcher could simply register a chain of objects, each of which can turn off/on a given interactor or list of interactors. When you want to change a mode, you pass a QString describing the mode name and each switcher can decide whether or not to respond to that token, registering/deregistering interactors as necessary. Does anyone have a thought on this? Is it already work in progress? Thanks Matt ------------------------------------------------------------------------------ Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
