The Client Settings configuration interface applies globally to the Display module and will take effect on the next startup.
The Portable Settings apply to all client types, and the WPF settings are only available to Windows WPF clients.
On this page:
In this context, a "Client" refers to a software application that serves as the user interface which interacting with the Solution Service (TWebService). The Client Settings configuration interface works as the access point for users, allowing them to manage, control, and monitor various functionalities of the service. Clients can range from desktop applications supporting multi-monitor setups to mobile or web interfaces, handle tasks like data exchange, operational control, security, and data integrity, ensuring secure and accurate communication with the solution service. The settings, such as layout and theme customization, multi-monitor support, and security parameters, enable users to personalize their experience based on individual needs and preferences.
Client Settings are configurable options like selecting a 'Dark' or 'Light' theme, choosing a 'Grid' or 'Freeform' layout, enabling view-only modes for web or Windows clients, and activating multi-monitor support for enhanced display options.
The purpose of these settings is to provide users with a customizable interface that meets their specific operational needs. They facilitate adaptability to different hardware setups, compliance with security standards, and enhancement of the overall user experience by allowing personalization of the application's look and functionality.
These settings enable users to modify how the application appears and operates on their devices. This includes choosing layouts, themes, adjusting how the software behaves in different quality and security scenarios, and setting up display options for monitoring and control.
Client Settings operate through user interaction with various configurable options. Users can select different layouts, themes, and view modes, define security and data quality preferences, and configure multi-monitor setups. These settings are particularly detailed for RichClients and SmartClients, offering advanced customization.
These settings are applicable in environments where software customization, data security, and efficient display management are important. This includes industrial control systems, enterprise data management, and scenarios requiring detailed monitoring and user-specific interface setups.
To use these settings, go to Displays → Client Settings. Here, they might enable multi-monitor support by checking a box and selecting '2' from a dropdown menu for the number of monitors. They could also navigate to security settings to specify how the software handles undefined or bad quality tags, ensuring data integrity.
Initial Execution Conditions | ||
Layout | Dropdown menu for selecting the initial layout | Allows users to choose the initial layout of the application. |
Theme | Dropdown menu with "Steel" as the current selection | Lets users select the visual theme of the application. |
ViewOnly | Options for restricting the view mode to web clients or Windows clients | Configures the application to restrict view mode to specific client types. |
Indications For Tag Quality And Security | ||
Handling Security Restrictions | Dropdown menus and checkboxes for security restrictions | Controls how the application responds to various security scenarios. |
Undefined Quality | Dropdown menu and checkboxes for undefined quality tags | Manages settings related to tags of undefined quality. |
Bad Quality Tags | Dropdown menu and checkboxes for bad quality tags | Determines how the application handles tags of bad quality. |
Enable Multiple Monitors (RichClients Only) | ||
Multi-Monitor Support | Checkbox to enable multi-monitor support | Enables multi-monitor support specifically for rich clients. |
Number of Monitors | Field to specify the number and dropdown to select the monitor and its layout | Allows specifying the number of monitors and selecting each monitor's layout for rich clients. |
Settings Available Only For RichClients And SmartClients (Windows) | ||
Layout Override | Dropdown with these default options: Startup, Dashboard, HTML5 LogOn, HTML5 Startup | Lets users select the layout that will override the client window. |
Startup Window Title | Text field labeled "Startup Window" | Allows users to set the title of the startup window. |
MinimizeBox | Checkbox to enable 'MinimizeBox' | Enables or disables the minimize button on the window. |
MaximizeBox | Checkbox to enable 'MaximizeBox' | Enables or disables the maximize button on the window. |
CloseBox | Checkbox to enable 'CloseBox' | Enables or disables the close button on the window. |
Resize | Checkbox to enable 'Start Maximized' | Enables or disables the resize functionality of the window. |
Start Maximized (Except in Development Profile) | Checkbox to enable 'Start Maximized' (Except in Development Profile) | Maximizes the application at startup, except in development mode. |
Show Menu | Checkbox to enable the 'Show Menu' option. | Shows or hides the main menu. Includes checkboxes for enabling/disabling File, Tools, and Security items. |
Always Shows Menu in Development Profile | Checkbox to enable menu visibility in the Development Profile | Ensures that menus are always visible in development profile mode. |
Mouse Cursor Visibility | Checkbox to enable 'Mouse Cursor Visible' | Toggles the visibility of the mouse cursor. |
On-screen Keyboard Activation | Checkbox to enable the 'On-screen Keyboard' | Activates an on-screen keyboard, ideal for touch-based interfaces. |
Define as Default Settings Button | Button labeled 'Set Default' | Resets settings to their default values. |
Multiple Windows Sharing User Logon | Checkbox to enable 'Multiple Windows Sharing User Logon' | Allows multiple windows on the same computer to share a user logon. |
At Displays > List you can setup global configuration for the behavior of the client displays, for .NET and HTML5 clients.
It includes the default Layout that will be opened by default, as well other settings that specific for the .NET or HTML5 clients.
<< The following sentence must be moved to the section ClientTypes, or event main page, to explain Why .NET clients, instead of only HTML5: Some advanced features, such as automatically blocking the ability to task switch is available only on .NET>>
Portable Clients Settings | |
---|---|
Field | Description |
Disable Commands | Select to prohibit application users from sending commands to the PLC. |
Desktop Initial Page | Select the display that desktops users see when they start the application. |
Mobile Initial Page | Select the display that mobile users see when they start the application. |
.NET Clients Settings | |
---|---|
Field | Description |
Maximize When Open | Select to maximize the client window to fit the monitor. |
Stretch | Select how the layout stretches when clients use the application:
|
Scrollbar | Select to have a scrollbar display in the client window. |
Title | Enter a title for the client window. |
MinimizeBox | Select to display the standard minimize button. |
MaximizeBox | Select to display the standard maximize button. |
CloseBox | Select to display the standard close button. |
ResizeBox | Select to display the standard resize handle. |
Menus | Select which menus to display:
|
Always shows titles and menus in Test Mode | Select to always show the Minimize, Maximize, Close, and Resize buttons when running a project in Test Mode. |
OnScreen KeyBoard | Select to display a virtual keyboard. |
When Mouse Is Over Command Areas | Select behavior when the mouse is over an object:
|
Mouse Cursor Visible | Select for the mouse pointer to be visible. |
Verify Tag Quality on Client Displays |
|
Disable Web Commands | Select to prohibit application users from sending commands to the PLC. |
Multiple windows on same computer share user logon | Users can run multiple instances of the application on the same computer. The user may need to log in as a different user from time to time. Select this option to automatically change the logged in user in all running instances of the application on the same computer. |
In this section: