Hi there Christian,
Thanks for the links. I have not fully digested them yet, and I agree with
Mikos that a migration guide would be helpful.
Right now however, I am a little worried that when I update my MITK to the
latest 13.03 release that our existing tools will be broken, and there will be
no way of immediately fixing them, so we would have to roll back to 12.12.
This means we lose the benefit of all the things that DKFZ worked on between
12.12 and 13.03. This would also affect any other group who had their own tools.
Is there any way to make 14829 available before the release so that there is a
short term, almost immediate upgrade solution, and a longer term upgrade to the
new framework?
I'll continue reading anyhow :-)
Thanks
M
On 26 Mar 2013, at 16:50, "Weber, Christian(1)"
<[email protected]<mailto:[email protected]>>
wrote:
Hi Matt,
I attached some links to the documentation of the new framework at the end, the
basic principles remain the same,
but there are quite some changes aimed to make interaction more flexible and
provide better configuration possibilities and a (hopefully ;) ) clearer way
for event distribution.
As for changing the mapping, this was only intended as a temporary way to avoid
the conflicts until the branch is merged, which should happen shortly after the
release (mid of April),
then the display interaction can be switched off while your interactions are
active.
Regards
Christian
General concept:
http://docs.mitk.org/nightly-qt4/DataInteractionPage.html
Some Implementation notes:
http://docs.mitk.org/nightly-qt4/DataInteractionTechnicalPage.html
Howto for interactions:
http://docs.mitk.org/nightly-qt4/Step10Page.html
Von: Clarkson, Matt [mailto:[email protected]<http://ucl.ac.uk>]
Gesendet: Dienstag, 26. März 2013 17:10
An: Weber, Christian(1)
Cc: Miklos Espak; mitk-users
Betreff: Re: [mitk-users] GlobalInteraction::INFORM_ONE
Hi Christian,
This is actually quite crucial for us to understand, as we have a number of our
own tools, implemented using the same type of interaction as the existing
paintbrush tool.
Are you suggesting that we change StateMachine.xml to define different mappings
for the interactors used in QmitkStdMultiWidget or, our tool? Either way, I
dont think this is very useful to us, because we would like to use for example
the right mouse button to zoom in/out, and the turn painting on, and use left,
middle and right mouse buttons to do various painting operations. Our users
already like this.
So, what is the estimated impact of the proposed framework changes? Is there a
documentation page on this?
And when might 14829 be merged to master?
I appreciate you are all working hard for the release… so thanks for looking
into this.
Thanks
Matt
On 26 Mar 2013, at 13:20, "Weber, Christian(1)"
<[email protected]<mailto:[email protected]>>
wrote:
Hi Miklos,
this is related to the transition of the interaction framework, since the paint
brush still is part of the old framework they do not communicate with each
other,
I entered a bug (Bug 14829) to implement a way for manually switching the
display interaction on/off for these cases.
As a hot fix, you can change the mouse events to which the display interactor
or the paint brush tool reacts to avoid that conflict,
if you need help doing this just let me know!
Regards
Christian
Von: Miklos Espak [mailto:[email protected]<http://gmail.com>]
Gesendet: Dienstag, 26. März 2013 13:20
An: mitk-users
Betreff: [mitk-users] GlobalInteraction::INFORM_ONE
Hi,
I want to disable the display geometry interactions (especially the shifting of
the image by the middle mouse button) while a paintbrush tool is turned on.
The event notification policy is set to INFORM_ONE by a
mitk::GlobalInteraction::GetInstance()->SetEventNotificationPolicy(mitk::GlobalInteraction::INFORM_ONE);
call when the tool is selected, and to INFORM_MULTIPLE when it is deselected.
This was working not so long ago, but now it is not. If the paintbrush tool is
on then the dragging with the middle mouse button triggers both the image
editing and the movement of the image.
What I know for sure that it worked in an older version of our app that was
based on the MITK 12.12 release.
I have seen that the interaction framework went through a fundamental redesign,
and the GlobalInteraction class is deprecated. Are the notification policies
not supported any more? What could I use instead of them?
Thank you,
Miklos
------------------------------------------------------------------------------
Own the Future-Intel® 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://p.sf.net/sfu/intel_levelupd2d_______________________________________________
mitk-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/mitk-users
------------------------------------------------------------------------------
Own the Future-Intel® 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://p.sf.net/sfu/intel_levelupd2d
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
