Symbol:
The visualization manager manages the configuration settings for all display variants of the visualizations of the current application.
The object is automatically inserted when a visualization object is inserted below the application. On a double-click the configuration dialog opens with several tabs.
Tab 'Visualization manager' – 'Settings'
Symbol:
Function: the tab contains settings for all visualizations that are available application-wide.
'General settings'
“Use unicode strings” |
|
“Use CurrentVisu variable” |
Requirement: the application contains a visualization that calls further visualizations. Example
|
'Style settings'
The “Visualization Style Editor” enables new styles to be generated, checked and installed in the visualization styles repository.
“Selected style” |
|
|
Opens a selection list with styles that are installed in the visualization styles repository. |
“Display all versions (for experts only)” |
|
Button |
Opens a selection list with commands for the use of the “Visualization Styles Editor”. |
“Open Style Editor” |
The “Visualization Styles Editor” opens. |
“Create and edit derived style” |
The “Visualization Styles Editor” opens with the dialog “Create a new visualization style”. The dialog contains the settings for the first configuration step. Requirement: a style is selected in “Selected style”. |
“Copy and edit the selected style” |
The “Visualization Style Editor” opens with the dialog “Open existing style as a copy”. The dialog contains the settings for the first configuration step. Requirement: a style is selected in “Selected style”. |
“Preview” |
The elements displayed represent the style specified in “Selected style”. |
'Language settings'
“Selected language” |
Language used by the display variants at the start of a visualization. |
'Settings for default text input'
For an element with standard text input, a dialog that supports the input appears at runtime. You can specify which dialog appears.
“Numpad” |
Dialog that calls the visualization if a user activates the input field for a number at runtime. The dialog represents a numeric keypad. Default: “VisuDialogs.Numpad” |
“Keypad” |
Dialog that calls the visualization if a user activates the input field for a text at runtime. The dialog represents a keyboard. Preset: “VisuDialogs.Keypad” |
“Use text input with limits” |
Requirement: CODESYS TargetVisu or CODESYS WebVisu are configured as display variants and the “standard text input” is “keyboard”. The visualization then supports input via keyboard at runtime. The input thus generally takes place via an input field.
Default:“VisuDialogs.TextinputWithLimits”. This dialog displays the value range and doesn't accept any value outside these limits. |
'Settings for user management dialogs'
You can configure your visualization with a user management. To do this, configure
an input to an element that causes a user management dialog to appear. The You can also use other visualizations as user management dialogs. To do that you have to change the defaults here. |
|
“Login dialog” |
User management dialog that enables logging in; typically a request to enter a username and a password. It appears upon an input event on an element that executes as a consequential action “User management”, action “Login”. Preset: |
“Change password dialog” |
User management dialog that enables a password to be changed; typically a request to enter the current password and a new one. It appears upon an input event on an element that executes as a consequential action “User management”, action “Change user password”. Preset: |
“Change configuration dialog” |
User management dialog that enables a configuration change of the user management, i.e. typically a display of the current user configuration and a possibility to change it. It appears upon an input event on an element that executes as a consequential action “User management”, action “Open user configuration”. Preset: |
'Additional settings'
“Activate multitouch handling” |
Elements concerned
|
“Activate semi-transparent drawing” |
To do this you can additionally specify a graduation value for the transparency when defining a color. The transparency is defined in the “Transparency” property. The leading byte is evaluated in color variables. Preset: Activated. Requirement: you create a new visualization and the display variants can paint semi-transparently. |
“Activate standard keyboard handling” |
|
'Extended settings'
“Size of memory for visualization” |
Memory size in bytes allocated by the visualization at runtime. Preset: “400000” |
“Size of the paintbuffer (per client)” |
Memory size in bytes allocated by the visualization per display variant and used for painting actions. Preset: “50000” |
“Transfer visualization files to the PLC” |
|
Use local visualization files |
Note: In order to achieve that the visualization can access the files stored locally, it is necessary thatthat the file paths are relative. The paths are given in dialog box “Project Project settings” in tab “Visualization”. Note: It is also necessary that the link type of a image is “Link to file”. The link type is specified in the image pool. |
See also
Display variant denotes the type of visualization, for example WebVisu, TargetVisu. A visualization client is a currently connected display medium. Thus, several browsers (clients) can be connected in parallel for the display variant WebVisu.
“Maximum number of visualization clients” |
Limits the number of visualization clients that are executed at the same time. If you configure the elements so that they vary depending on the display variant,
then you have to limit the number of display variants. A visualization is given an
ID at runtime that identifies the display variant and then processes data accordingly.
CODESYS can the query the ID using the system variable Example: Requirement: Tip: You can find in the CODESYS store. example "Global Client Manager" |
“Transfer both svg images and converted images” |
This option is visible only if both a WebVisu and a TargetVisu exist. It concerns images in svg format only. The option is available if the device description for the controller of the TargetVisu does not support the svg (full) format.
|
Not all settings are available with an integrated CODESYS visualization.