Background colors can be very useful when the Screen's drawing does not measure up to the required sizes for the Screen window. Therefore by using a background colour you can effectively hide the difference between the window's borders.
Movicon Help on Line - Rel. 11.7.1301
By using the Background properties you can define the properties concerning the Screen window's background. To do this just select and open the required Screen and then edit its settings through the Movicon 'Properties Window'.
You may find it useful to set a different background colour to that proposed for default. Screen backgrounds do not have to be made up of drawings: Movicon Screens can also be made up with controls only (buttons, displays, graphics, etc), therefore the background need simply be a uniform colour.
|
|
Background colors can be very useful when the Screen's drawing does not measure up to the required sizes for the Screen window. Therefore by using a background colour you can effectively hide the difference between the window's borders. |
By using this dialog box you can associate a static image in BMP, JPG, GIF, WMF type, etc. as the Screen's background. As an alternative to entering the path and name, you can select the file by using the '...' browse command button found at the side of the edit box.
|
|
Pressing the "CRTL + (...)" keys consents to editing the selected background image, by opening the predefined application associated to that image in a new window. |
This edit box is used for entering the X coordinates in pixels of the eventual background image's position associated to the Screen window.
The coordinate refers to the position of the image's highest left corner in relation to the Screen's highest left corner (being X0).
This edit box is used for entering the Y coordinated in pixels of the eventual background image's position associated to the Screen window.
The coordinate refers to the position of the image's highest left apex in relation to the Screen's highest left apex (being X0).
Delay in milliseconds before Movicon unloads the Screen from memory after changing pages. When executing a change page with two Screens open in MDI mode, the one which is closed is only hidden and will be destroyed after this time has been exceeded (unloaded from RAM). When the value is set at '0' the Screen will be unloaded immediately and then the next screen will be loaded.
By using this selection you can set the background colour shades associated to the Screen. The shades of colour can be selected from those proposed on the drop-down list (horizontal, vertical shades etc).
The shades of colour are a combination of the 'Background Color' associated to the Screen and the one selected from the 'Gradient Color' property.
The 'none' option means that no shades of colour have been associated to the Screen.
By using this selection you can define the colour for the Screen's background gradient. The resulting various shades of colour will be a combination of the 'Background Color' associated to the Screen and the one selected from the 'Gradient Color' property.
By using this edit box you can define the width in pixels with which the background associated to the Screen is to be displayed. When using the '-1' value the image will be displayed with its default size, otherwise the image will be resized according to the sizes set but with the possibility of losing its graphical quality.
By using this edit box you can define the height in pixels with which the background associated to the Screen is to be displayed. When using the '-1' value the image will be displayed with its default size, otherwise the image will be resized according to the sizes set but with the possibility of losing its graphical quality.
If the associated file as background colour is the right size this selection permits the image to be repeatedly displayed along side each other in the Screen until the whole area in the window is covered.
Each Screen processes the logics and tasks associated in the User Interface thread. When this option is active, the Screen will execute in a separate thread, independently from other project threads. This is handy to use when there are Screens containing significant logic or synapses processes. In this case the logic processing will be executed in a separate thread without penalizing the graphic interface, which nevertheless requires a greater commitment of the memory resources.
|
|
The 'Chart' object cannot be used in screens opened in a separate thread (Screen 'Spawn Thread Execution' property). In cases contrary to this, the 'Chart9 object will not appear on screen and the following error message will appear in the output window:
Failed to create chart. Make sure the object isn't inside a synoptic with the separate thread option
|
Enabling this property, only the first user who get connected to the screen resource can have write access to that screen. All other users who get connected can only open the screen but can not give commands, like setting a variable value using a display, potentiometer, etc. or acting on button commands like page change etc. This mode allows to avoid that simultaneous connections can write the same variable. As an example, if in Server project a user has opened the "LayOut" screen, any other WebClient user who get connected to the same screen could not have write access to that screen. Vice-versa the rule is valid even if the WebClient user first accesses the screen. In this case the local user of the Server project will not have write access to that screen. When a user opens a screen already opened with exclusive access by another user, a warning message will appear, as follows:
The screen 'ScreenName' cannot be opened with the exclusive Write Access
Subsequnet Users who access the screen protected with Exclusive Write Access will only be able to activate command through a resource outside of the screen context such as: Menus, Shortcuts, Basic Script, Event Objects, Alarms, etc.. This means that once entering a screen with Exclusive Write Access, the user will have to use a command from the Menu or Shortcut in order to exit. However, Web Client users who do not have these resources at their disposal will have to restart the applet to reconnect to the project with a new session (and then try to re-access the screen with Exclusive Write Access).
