Movicon Help on Line - Rel. 11.7.1301
By using the Execution properties you can define the Screen's advanced functionalities. In order to do this just select and open the Screen required and then edit its settings through the Movicon 'Properties Window'.
If required by using this edit box you can select a variable from the Movicon Real Time DB which determines the number of display layers for the Screen's controls and symbols. If you want to manage the layers, each Movicon drawing or symbol must be declared with the required level by using the 'Layer' property from the control's or symbol's 'Properties Window'.
A Screen can have up to 32 layers. Therefore it is essential that the variable defining the number of layers must be in DoubleWord (32 bit), keeping in mind that each single bit corresponds to the displaying of the layer relating to that number, starting from zero bit which corresponds to the first layer.
|
|
Activating one layer will not exclude another, which means that there can be many levels active at the same time based on the bit set in the logic state '1' in the associated variable. In addition to this, the 16 available levels do not have any priority hierarchy over each other. |
The base Screen's name for the Public Symbols is entered in this dialog box. The Movicon controls and symbols can infact be associated a 'Public Name'. When some symbols with the same 'Public Name' have been inserted into the project, and one of these is present in the 'Public Symbols Container', all the public symbols will be modified with the base symbol's properties, being the one contained in the Screen specified in the 'Public Symbols Container' property, at the Runtime startup. These modifications only take place in Runtime, therefore the symbols will resume their original properties when returning back into planning mode.
By using this property you can select a screen to use as a style source container. For further information on how this property works please refer to "Style Sources in Symbols".
When enabling this property activates a management that puts 'Inuse' variables out of use (Not in use) when the object they are being used in becomes INVISIBLE on screen for more than 5 seconds (not editable) and as a consequence these variables will no longer be exchanged with the field and not counted by the license. As soon as the object becomes visible again, its variables will return back in use.
The object's variables will change to NOT in use when the object comes invisible due to one of the following reasons:
Visibility management performed through object's "Animation - Visible" property
Visibility management performed through using "Screen Levels". In this case you must set the object's "Visibility - Level" property
Visibility management performed through enabling the zoom factor (object's "Visibility - Control Zoom" and "Visibility - Percent Zoom/Size" properties)
Visibility management performed through enabling scale factors (object's "Visibility - Control Size" and "Visibility - Percent Zoom/Size" properties). In this case the object's "Animation - Size" property should also be set appropriately
Visibility management performed through user " Access Levels". In this case the object's "Access Levels- Read Access Levels" property should be set appropriately
Visibility management performed through object's "Visibility - Visible on Web Client" option
Visibility management performed through object's "Visibility - Visible on WinCE" option
|
|
Caution! Variables used in the "Animation - Visibility" and "Animation - Size" properties remain always In Use even when object is invisible. This is due to the obvious reason that once the object has been made invisible by one of these properties, it can return visible when the variable changes again. |
|
|
The variables In use management is not performed for the "Animation - Transparency" property. If the object should become completely transparent (associated variable value equal to zero) the variable should remain in use because in this case it's the object's transparency that is being managed and not its visibility. |
All the object's variables are subject to being placed in NOT In Use when object is not visible. These variables are those used in the following object's resouces:
variables used in the object's dynamic properties
variables used in the object's Command Lists
variables used in the object's IL logic
variables used in the object's script code
variables used in the object's script code's "Variable Events" . In this case the variable's variation will not execute the associated event.
When the 'Inuse Objects Manage' is enabled, when no longer visible, some objects will obtain certain behaviours in they way they work when their variables are Not in use. The objects involved and their behaviours are as follows:
Button Objects: when a button becomes invisible, the timer that controls the "Impulsive" or "Commands While Down" commands is terminated. This means that the command in execution will be aborted.
Trend Object: when a Trend becomes invisible, the value recording facility in the Trend buffer is stopped as well as the recording of data in any preset ".csv" files. This means that, if the Trend is not connected to a DataLogger, no data will be recorded while the objectremains invisible. When the Trend returns back to being visible, it will show data recorded beforehand and commence adding new data as it is recorded. If the Trend has been set to record on ".csv" file, the "Execution - Record on File" file, with the "Execution - Create New File" property enabled, each time the Trend is made invisible the ".csv" file will close and another one will be created when Trend returns back visible. This means that each time the Trend returns to visible mode, its data buffer will result empty due to the fact that a new ".csv" file has just been created.
Enabling this property permits the Screen's child objects be published in DOM format (Document Object Model, XML).
By enabling this property, the screen will inherit the back color of the active style source container. For further information on how this property works see "Style Sources in Symbols".
When enabled this property activates the execution of any synapses logic upon Screen loading.
When enabled this property activates the cyclic execution of any synapses logic when the Screen is active.
This property, if set with a value higher than 1, opens more than one instances in Pop-Up mode in the same screen. Once the set number of instances has been reached an error message in the log system will be alerted. this message only appears when the maximum number of Pop-Up instances set in the property is more that one, otherwise no error message will show and the screen already opened will obtain focus.
|
|
Warning! Opening more than one instance in a screen may occur only when the screen is opened using the "Open Frame (multi-monitor)" command. Therefore, not more than one instance can be opened in the same window such as Popup modals. |
|
|
When the "Exclusive Write Access " property is enabled, only the first screen instance will have write access denying access to all others. For further information please refer to the chapter on "Screen Background Properties" |
|
|
Opening a screen in more than one instance is NOT supported in Windows CE. |
The "Enable Multi-touch" property from the Screen "Execution-Advanced" property group allows you to click more than one object at the same time eg. two buttons that each execute command lists. In this case, Movicon will not have to interpret gesture messaging but the execution of two commands upon being pressed.
