I still don't understand your scenario, sorry. What do you connect exactly? 
What do you trigger exactly? Why is your interactor located in the plugin? What 
data do you mean? An mitk::BaseData derived class or just a simple random data 
type? Anyways, in most cases I would still give the same answer I guess. If you 
don't derive somehow from MITK or ITK, you would have to implement your own 
observer pattern, though.

Best,
Stefan


-----Original Message-----
From: Florian Jung [mailto:florian.j...@igd.fraunhofer.de] 
Sent: Dienstag, 16. August 2016 17:19
To: Kislinskiy, Stefan; mitk-users
Subject: Re: [mitk-users] New interactor concept, how to access data after 
procession

I'll try it in a bit more detail:

I have a algorithm in module.
I connect an interactor from a plugin with the module.
I triggered the plugin through the interactor, the data is processed and lies 
within the module.
How should the module notify the plugin that the data is processed, so the 
plugin can fetch the processed data?

Am 16.08.2016 um 16:54 schrieb Kislinskiy, Stefan:
> Hi,
>
> I'm not sure if I really understood your scenario. You trigger an algorithm 
> that runs in another thread and you want to get informed when the work is 
> done? There are different general strategies for async programming but you 
> could start by listen to the modified event of the data you are manipulating 
> in your algorithm? As MITK "derives from ITK", most of our classes provide 
> the possibility to be observed (modified and delete events). Depending on 
> your scenario you can also try to work with Qt Threads.
>
> Best,
> Stefan
>
>
> -----Original Message-----
> From: Florian Jung [mailto:florian.j...@igd.fraunhofer.de]
> Sent: Dienstag, 16. August 2016 15:46
> To: mitk-users
> Subject: [mitk-users] New interactor concept, how to access data after 
> procession
>
> We move/have moved several plugins to modules.
> Most things worked without a problem.
>
> But there is still one scenario, which I don't know how to design it properly.
>
> I add an interactor within the plugin.
> The interactor catches a mouseclick and does some image processing within the 
> module.
>
> Now the question. Once the module is finished, how can I inform the plugin 
> that the processing is finished, because the module has no knowledge about 
> the plugin.
> Obviously something like a observer pattern is needed.
> Is there an example in the code for this or can somebody tell me, how 
> something like this is best implemented in mitk?
>
> Best regards
> Florian
>
> --
> Florian Jung
> Department Visual Healthcare Technologies
>
> Fraunhofer-Institute for Computer Graphics Research IGD Fraunhoferstr. 
> 5, 64283 Darmstadt, Germany
>
> phone:  +49.6151.155.520
> fax:    +49.6151.155.480
> email:  florian.j...@igd.fraunhofer.de
> web:    http://www.igd.fraunhofer.de
>
>
> ----------------------------------------------------------------------
> -------- _______________________________________________
> mitk-users mailing list
> mitk-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/mitk-users


--
Florian Jung
Department Visual Healthcare Technologies

Fraunhofer-Institute for Computer Graphics Research IGD Fraunhoferstr. 5, 64283 
Darmstadt, Germany

phone:  +49.6151.155.520
fax:    +49.6151.155.480
email:  florian.j...@igd.fraunhofer.de
web:    http://www.igd.fraunhofer.de


------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

------------------------------------------------------------------------------
_______________________________________________
mitk-users mailing list
mitk-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mitk-users

Reply via email to