A Situational Awareness project can be configured to support multiple screen resolutions using two methods:
At runtime, when a request is made to display a page, the workspace will first look for a page that has a resolution extension that matches the resolution of the host workspace master page. If a version of the page with the requested extension does not exist, it will next attempt to display a page without an extension.
Both these methods allows clients to use the same project configuration (including menus, equipment and pages) on different resolution screens.
You can mix and match these methods in your project. For example, you may decide that 90% of your mimics can be shared across resolutions, but 10% need to be optimized for HD and UHD resolutions.
Create content that can be shared across screen resolutions
In most cases, the content you create will successfully adjust based upon the Display Mode of the pane it is displayed in (see Configure Panes on a Master Page).
If you want to share content across resolutions, do not add a resolution suffix to your faceplate or page names.
Explicitly define content for a particular resolution
In some cases it may be necessary to explicitly create content to suit a particular resolution. For example, if you mostly have UHD4K monitors in a plant and just a few HD1080 monitors, you will want your project's content to take advantage of the available screen space on the UHD4K screens. However, you may need to create an HD1080 version of some pages for the content to display appropriately on a smaller screen. If this is the case, you could create an HD1080 version of any pages that needs to be adjusted.
Two screen resolutions are supported in this way:
To create content that is specific to a resolution, add one of the following extensions to the end of your faceplate or page names.
For example, you could create the following variations of the same content page:
At runtime, the extension that matches the resolution of the host workspace master page will be used.
The feature also requires that anywhere a page name is called, such as the Target Page field of a menu, the extension needs to be left off the page name. The workspace will read the page name and automatically look for a version that has a matching resolution suffix.
This feature applies to:
Note: When using this feature, you need to be careful not to specify a full page name (with the resolution prefix) when calling a page. This is particularly true when using Citect Studio, as the interface allows you to select a full page name.
See also
Published June 2018