-
Notifications
You must be signed in to change notification settings - Fork 4
Silent Workflow Execution
Dahie edited this page Apr 21, 2011
·
2 revisions
Up until version 1.2 during workflow execution ImageFlow always launched a visible ImageJ instance. The ImageJ GUI appeared, executing the generated MacroCode. ImageJ would display the results and and there is no callback to ImageFlow.
In version 1.3 the Silent workflow execution is introduced, that allows to execute workflows as a background-process of ImageFlow and to receive advanced callbacks from ImageJ to display results within ImageFlow, for example as Preview-Images on each processing node.
tbd
tbd