Module.GetLastErrorMessage (METH) ¶ METHOD GetLastErrorMessage : STRING(255) InOut: Scope Name Type Return GetLastErrorMessage STRING(255) Input sLanguage STRING

Module.LastErrorInstance (PROP) ¶ PROPERTY LastErrorInstance : IModule returns the interface of the module instance that has caused the last error. 0 means: the error occured in this module instance or no error has occured.

Module.LastErrorNumber (PROP) ¶ PROPERTY LastErrorNumber : UINT

Module.ReportError (METH) ¶ METHOD ReportError InOut: Scope Name Type Input uiErrorNumber UINT itfErrorSourceModule IModule

Identification ¶ Environment (Property) Handle (Property) ModuleInfo (Property) SetIdentification (Method)

Module.Environment (PROP) ¶ PROPERTY FINAL Environment : POINTER TO MEnv

Module.Handle (PROP) ¶ PROPERTY FINAL Handle : ModuleHandle

Module.ModuleInfo (PROP) ¶ PROPERTY FINAL ModuleInfo : POINTER TO ModuleInfo

IRmpService2.GetIsActionOngoing (METH) ¶ METHOD GetIsActionOngoing : BOOL This method determines if this channel (for RMP) is currently active writing or reading. ..note: Do not perform an action without checking for avitivity first. This is especially important when using multi-threading (especially on multi-core systems). Whenever an action is ongoing, one should omit to do any work on variables used in the RMP (for example as mirror variables). In the case of an action is ongoing and you want to work on RMP variables, just wait as amny cycles as necessary, until no action is ongoing any more. Then when working on the variables use IRmpService2.SetIsActionOngoing to ensure, that AC generated code will not interfere with your work on the RMP variables. ..return: If it was possible to get the current state of activity. If this is FALSE xIsActionOngoing is not valid! InOut: Scope Name Type Comment Return GetIsActionOngoing BOOL Output xIsActionOngoing BOOL Whether the RMPService is currently active.

IRmpService2.SetIsActionOngoing (METH) ¶ METHOD SetIsActionOngoing : BOOL This method tries to set that this channel (for RMP) is currently active writing or reading. ..note: Do not start an activity without setting the flag by this method! And do not forget to reset it after finishing. This is especially important when using multi-threading (especially on multi-core systems). Whenever an action is ongoing, one should omit to do any work on variables used in the RMP (for example as mirror variables). In the case of an action is ongoing and you want to work on RMP variables, just wait as many cycles as necessary, until no action is ongoing any more. Then when working on the variables use IRmpService2.SetIsActionOngoing to ensure, that AC generated code will not interfere with your work on the RMP variables. ..return: If it was possible to set the current state of activity. If this is FALSE xIsActionOngoing has not been set! InOut: Scope Name Type Return SetIsActionOngoing BOOL Input xIsActionOngoing BOOL