executeNewCallChain
Syntax
&MyMethod.executeNewCallChain([Argument1:any, …[,@:object=@, ?:object=self]]) |
The method executeNewCallChain executes the referenced Method after Plant Simulation processed all active call chains. The effect is similar to &Method.executeIn(0). Let's say you schedule a method in a reset method with executeNewCallChain, the scheduled method will only be executed after all already scheduled methods have been finished.
When executing a method triggers controls, Plant Simulation interrupts the method and executes the controls. Let's say that the instruction @.move triggers an entrance control and an importer request control. The interrupted method will only be continued, after these controls have been processed all the way. If one of the controls schedules a new method with executeNewCallChain, this method will be executed after controls have been executed, but before interrupted method will be continued.
The method executeNewCallChain behaves differently than the method executeIn(0). The difference is that executeIn requires an EventController and that a method, that was scheduled with &Method.executeIn(0) will only be executed after the already scheduled simultaneous events.
In the called method the anonymous identifier ? references the caller, i. e., the method, which contained the method executeNewCallChain, or, if the caller is a user-defined attribute of data type method, to the location of the user-defined attribute.
Parameter
The optional parameters ArgumentN designate the arguments which are to be executed.
You can also enter two additional parameters of data type object. In this case the last two parameters are assigned to the anonymous identifiers @ and ?.
Syntax
var o : object := .Models.Model.&MyMethodWithoutParameters |
Related Topic