ViewX Inset Close Is Registry-Controlled, Not Tab-Controlled

After the registry value is enabled and ViewX is restarted, mimics opened as inset windows display a close control on the right-hand side. The existing current-tab indication remains visible, so the added chrome consumes some display area.

Build and client applicability

The term inset window chrome here means the visible window controls added around a mimic opened as an inset. This change applies to the ViewX client and does not describe a server-side database setting or a property stored on an individual mimic.

Use the installed build date as the first compatibility check. The setting was reported to appear in December 2018 builds onward and was directly observed in a 2017 R3 Feb 2019 build. The release-family name alone can therefore be misleading: a 2017 R3 installation may contain a later maintenance build that implements the option.

1. Identify the ViewX release and build date from the installed client.
2. Confirm that the target display is a mimic opened as an inset rather than another ViewX window type.
3. Record the current ViewX behavior before changing the registry.

Check 1: Expect an eligible ViewX build and an inset mimic that currently lacks the required right-side close control.

Registry scope and value definition

The configuration resides under the 32-bit application registry branch on the ViewX workstation:

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Schneider Electric\ClearSCADA\ViewX

Create the following value beneath that key:

Wow6432Node is part of the required path. Editing a similarly named path elsewhere does not configure the same application registry location. Because the scope is HKEY_LOCAL_MACHINE, apply the change to every ViewX workstation that requires the behavior; changing one workstation does not configure other clients.

Check 2: Expect the parent path to end in ClearSCADA\ViewX, with no duplicate value of a different registry type.

DWORD creation procedure

Close ViewX before commissioning the setting so the test begins from a known client state. Use the Windows Registry Editor with credentials permitted to modify the machine-level branch. Record whether the value already exists before overwriting it; that record provides a direct rollback reference.

1. Open the Registry Editor on the ViewX client workstation.
2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Schneider Electric\ClearSCADA\ViewX.
3. Create a DWORD value named exactly InsetWindowsHaveChrome. Registry value spelling matters; avoid spaces or alternate capitalization.
4. Set the value data to 1.
5. Read the entry back before leaving the editor.

The wrong practice is to create a string containing “1.” The required type is a DWORD, and the numeric data is 1. Likewise, creating the value under a user-specific branch changes the scope and does not reproduce the documented machine-level configuration.

Check 3: Expect InsetWindowsHaveChrome to appear as a DWORD with value data 1 under the exact ViewX key.

ViewX restart and functional inspection

ViewX must restart after the registry edit. A mimic refresh or navigation to another display is not the specified activation step because the client reads the configuration as part of its startup behavior.

1. Exit ViewX completely.
2. Start ViewX again on the modified workstation.
3. Open a known mimic using the inset presentation.
4. Inspect the right-hand side of the inset for the close control.
5. Operate the control and confirm that it closes the inset rather than producing no action.

If the control does not appear, first read back the exact path, type, name, and data. Next confirm that ViewX was fully restarted and that the test object actually opened as an inset. If all four conditions are correct, compare the installed build date with the stated December 2018 applicability point.

Check 4: Expect the restarted client to show a functional close control on the right side of an inset mimic.

Layout impact and operator acceptance

Enabling the option does not replace the current-tab indication. Both remain visible, which reduces the area available to the inset content and may make the presentation look crowded. Evaluate this tradeoff at the display resolution and scaling used by operators rather than on an engineering workstation with a different desktop layout.

To reverse the presentation, set InsetWindowsHaveChrome back to its default value of 0 and restart ViewX. Retain the value as a DWORD during a controlled rollback so the before-and-after states remain explicit.

Check 5: Expect operators to retain the current-tab indication while gaining the close control, with the reduced inset display area accepted at the production resolution.

End-to-end commissioning verification

1. Registry check: Expect InsetWindowsHaveChrome to be a DWORD containing 1 at the exact machine-level ViewX path.
2. Startup check: Expect ViewX to complete a full restart after the edit.
3. Presentation check: Expect a mimic opened as an inset to show the close control on its right-hand side.
4. Operation check: Expect the close control to dismiss the inset when selected.
5. Layout check: Expect the current-tab indication to remain visible and the usable display area to be slightly smaller.
6. Scope check: Expect the change only on workstations where the machine-level value was commissioned.

FAQ