Page History

Client Setting Configuration

The Client Settings are organized into the following sections:

Initial Execution Conditions

It refers to a configuration group that defines the startup layout and theme. Its purpose is to initialize the application interface according to user preferences or operational needs. It allows for selecting layouts and themes and restricts views to web or Windows clients. Users can apply these settings in scenarios requiring specific startup interfaces. Before usage, ensure that predefined layouts and themes exist. Use this group to set initial conditions for application startup.

Image Removed

Indications for Tag Quality and Security

It refers to the definitions group, which configures visual indicators related to tag quality and security restrictions. Its purpose is to provide clear cues for identifying quality and security issues. Main functionalities include setting symbols for security restrictions and enabling indicators for undefined and bad-quality tags. This is useful in environments where visual feedback is needed to monitor system integrity. Configure it by selecting appropriate symbols. Use this group to set visual indicators.

Platform Restrictions

• On WebClients - Restrict to web browsers only
• On Windows - Restrict to desktop clients only

Tag Quality and Security Indicators

Visual feedback for data integrity and access control.

Security Restrictions

Display symbols when access denied:

• V - View only
• ? - Unknown security
• $ - Premium feature
• * - Restricted
• # - Protected
• Strikethrough - Disabled

Quality Indicators

Image Added

Multi-Monitor Configuration (RichClients)

Enable Multiple Displays

? Enable Multiple Monitors
Number of Monitors: 4

Monitor Assignment

Windows Client Settings

Window Controls

Menu Visibility

Always visible in Development profile.

Image Added

Special Features

Mouse Cursor

Control cursor visibility and type:

• Visible - Normal operation
• Hidden - Kiosk mode
• Active Area - Edge detection

Active Area Mouse Types

• None - Default system cursor
• Arrow - Standard pointer
• Hand - Interactive indicator

On-Screen Keyboard

Enable for touchscreen operation:

csharp

// Show keyboard with password masking
ShowOnScreenKeyboard(
    objectName: "PasswordField",
    isPassword: true,
    callback: (ok, tag, oldVal, newVal) => {
        if (ok) ProcessLogin(newVal);
    }
);

Title Bar Configuration

Custom Title

csharp

// Set runtime window title
@Client.Title = $"Plant Monitor - {DateTime.Now:yyyy-MM-dd}";

Title Options

• Enable/disable title bar
• Custom text
• Dynamic updates
• Include user/station info

Multi-Window Support

Allow multiple windows per user:

? Multiple windows on the same computer

Benefits:

• Single login for all windows
• Shared session state
• Independent displays
• Synchronized data

Runtime Properties

License Information

csharp

// Check allowed clients
int maxClients = @Info.License.AllowedRichClients;

// Monitor active sessions
int activeClients = @Server.TotalClients;

// Available slots
int available = maxClients - activeClients;

Best Practices

1. Set Appropriate Defaults - Match typical use case
2. Configure Quality Indicators - Clear visual feedback
3. Plan Multi-Monitor - Logical layout distribution
4. Test Platform Restrictions - Verify access control
5. Document Settings - Explain configuration choices
6. Consider Touch Operation - Enable keyboard if needed
7. Secure Kiosk Mode - Disable window controls

Platform-Specific Settings

Web Clients

• No multi-monitor support
• Limited window control
• Browser-based restrictions

Windows Clients

• Full multi-monitor
• Complete window control
• Native keyboard support

Mobile Clients

• Single display only
• Touch optimized
• Auto-rotation support

Troubleshooting

Layout not loading:

• Verify layout exists
• Check platform compatibility
• Review ViewOnly settings
• Test default layout

Quality indicators missing:

• Enable indicators in settings
• Check tag quality values
• Verify communication status
• Review symbol configuration

Multi-monitor issues:

• Confirm monitor count
• Check graphics drivers
• Verify layout assignments
• Test individual monitors

Keyboard not showing:

• Enable OnScreen Keyboard
• Check touch support
• Verify focus handling
• Test input methods

In this section...

Enable Multiple Monitors (RichClients Only)

It refers to a configuration group that allows multiple monitors with RichClients to be used. Its purpose is to enhance display capabilities. It enables the specification of the number of monitors and the selection of the target display for the startup layout. This applies to scenarios requiring extensive display areas, such as control rooms. Before usage, ensure that the system supports multiple monitors. Use this group to configure and optimize multi-monitor setups.

Settings available only for RichClients and SmartClients (Windows)

This group provides configuration settings reserved for RichClients and SmartClients on Windows. Its purpose is to customize the user interface. Main functionalities include overriding layouts, setting window properties, and managing menu and cursor visibility. Applications include customizing the interface for different operational requirements. Before usage, ensure that predefined layouts and properties are available. Use this group to tailor the UI for specific needs.

Image Removed

Masking Password when OnScreen Keyboard is available

To mask password input, set the parameter isPassword , from the OnScreen Keyboard method, to true when calling this method, as shown below.

/// <summary>
/// Displays screen keyboard
/// </summary>
/// <param name="objectName">Object name</param>
/// <param name="isPassword">Flag indicating whether is a password</param>
/// <param name="_actionShowOnScreenKeyboardOptional">Method called when dialog is closed. Prototyp: void Action(bool ok, string tagName, string oldValue, string newValue) </param>

public static void ShowOnScreenKeyboard(string objectName, bool isPassword, Action<bool, string, string, string> _actionShowOnScreenKeyboardOptional = null)

Operating clients available at runtime

This information comes directly from the license, and can be checked at runtime in the @Info.License.AllowedRichClients property, indicating how many clients can be opened in total, including RichClient, SmartClient and HTML5Client.

The @Info.License.AllowedWebClients property is deprecated and exists only for compatibility reasons, its value will always be 0.

In this section: