The below listed WinWrap functions are not supported when the script's "Use User interface" property is not activated and cause an error when the AppActivate ,AboutWinWrapBasic,Shell,ShowPopupMenu script code is being loaded.
Movicon Help on Line - Rel. 11.7.1301
By using the "Mode" properties you can set the modalities with which the script will be executed.
To change the Mode properties of a Basic Script, select the object with the mouse and use the Movicon "Properties Window".
This property is to be used when the Redundancy between two projects is used. When enabled the script will be executed only in the project which has control at that moment. If, for instance, both the Primary and Secondary projects are being run, the Primary project will be in control. In this case, even though the execution of the Basic Script is commanded from the Secondary project it will be executed in the Primary project.
This management also happens when the script is executed from a "Child Project" set to connect to a "Network Server". Also in this situation the script is executed in the "Network Server" project instead of the Child Project.
This setting allows you to add the user interface management to the basic script. You need to enable this property when using controls such as "MsgBox" or "Dialog Box" inside the Basic Script.
|
|
The below listed WinWrap functions are not supported when the script's "Use User interface" property is not activated and cause an error when the AppActivate ,AboutWinWrapBasic,Shell,ShowPopupMenu script code is being loaded. |
This selection allows you to execute the Basin routine in a separate thread, therefore also at the same time as another basic routine or process on the same thread (dialog window).
This option is used when the basic script is run while another is already being run. If this option is not checked in both these basic scripts, the running of the second one will be buffered and run when the first one has terminated.
Please be reminded that not all the Movicon functions are available when run in a separate thread. Therefore we advise you to refer to the guide for each instruction to verify whether it can be executed or not in a separate thread.
|
|
Great care needs to be taken to the Scripts which do not use separate threads but have long operations to carry out. These Scripts are put in the same thread which they share (limited resource consumption), where they are, however, queued up in line for execution. Therefore you need to check the "Separate Thread" option for Scripts which execute long operations. |
When this option box is enabled, a TAB will be created in the custom Output window, for the Basic Script during runtime mode, where messages inherent to the script are printed ie. the Debug.Print.
When this option is enabled, the Dialog windows opened by the script can be made modal. Otherwise the dialog windows will not be modal and will disappear into the background when clicked outside.
