The display interactors get the position events from any renderer. This was
actually a problem, since we have several viewers, and the interactor of
each one received the events from the others. So, now the display
interactors get in their constructor which renderers they need to handle so
that they can ignore any event that comes from a different renderer.
(See mitk::DnDDisplayInteractor::Notify() )
They definitely receive the position event from the 3D windows, too.
This might be different for data interactors.
On 13 September 2014 11:20, Clarkson, Matt <[email protected]> wrote:
> Hi there,
>
> can someone remind me: (yes, Im being a bit lazy).
> Following this: http://www.mitk.org/ViewsWithoutMultiWidget
>
> How is it that the Point Set Interaction picks up 3D click positions in
> both the 2D windows and 3D windows.
> Point Set Interaction also still depends on org.mitk.gui.qt.common.legacy,
> so what should be the correct way to pick up position events from Any
> render window.
>
> Thanks
>
> M
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> mitk-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mitk-users
>
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
mitk-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mitk-users
