Procedures for the Execution Context

The interface procedure described below can be used to get the execution context of a tool. The execution context gives information about the type of the execution. We distinguish between the execution contexts "Running" and "Unknown". The execution context is "Running" in case the execution of the custom tool was triggered because the execution of the respective MERLIC Vision App was started. This applies to all the ways of starting the execution of an MVApp, e.g., if the execution was started from the user by clicking the buttons for a single or continuous execution in the MERLIC Creator or if the execution was started in MERLIC RTE mode via a Communicator plug-in. For all other types of executions, the execution context is "Unknown", e.g., if the execution was triggered automatically because the user changed the value of a tool parameter in the MERLIC Creator or because the custom tool was loaded when opening a MERLIC Vision App containing the custom tool.

Currently, only one procedure is available to query the execution context. If you want to test if the behavior of the custom tool is correctly implemented with the test procedure MeTest_set_execution_context_to_running and MeTest_set_execution_context_to_unknown. You can use these procedures in your HDevelop test program to check if the tool works as desired in the different execution contexts.

Procedures