Difference: DpHipePluginsDeveloperManual (33 vs. 34)

Revision 342014-06-24 - AlvarGarcia

Line: 1 to 1
 
META TOPICPARENT name="DpHipePlugins"
<-- ANALYTICS CODE - DO NOT EDIT -->
<-- Google Analytics script BEGIN -->
<-- Google Analytics script END -->
Line: 415 to 415
  In principle, all plug-ins are started when HIPE is started, and presumably you will also register your PluginProcessor when HIPE is started. This gives rise to a race condition: Depending on whether you manage to register the processor a little bit earlier or later, it may or may not get called for some of the plug-ins. This is solved by making sure that all PluginProcessors that are registered are also called for all plug-ins that have been started already. Effectively this simply means you do not have to worry about this; if you register your processor, it will be called for all plug-ins that have been started and those that will still be started during HIPE start-up.
Added:
>
>

Further information

For any questions regarding plug-in development, please send an email to Alvar.Garcia@sciops.esa.int.

Original author: Paul Balm - 27 Aug 2010

 
Deleted:
<
<
-- PaulBalm - 27 Aug 2010
 
<-- COMMENT BOX CODE - DO NOT EDIT -->
 
This site is powered by the TWiki collaboration platform Powered by Perl