Each widget is created from two or more graphic files. The minimum requirement is for two images, one used when the value is in the "Off" state and one used when it is in the "On" state. All images for each widget must be the same size and of the same file format.
File formats supported are BMP, JPG, PNG, or SVG. Animated SVG files allow the graphic to appear move when in a particular state, e.g. a spinning fan graphics, which appear s to spin when on and stationary when off. The graphic file kept outside the folder is not supported by an easy palette.
Folder Naming
The image file names are not important, but the folders must be named using the following conventions:
Example: To create a folder called 'Coils' the folder should be named 'Folder_Coils'.
Each folder prefixed with ‘Widget_’ must contain at least two subfolders:
Any folder name prefixed with ‘Widget_’ will define an instance of a widget. The name of the resulting widget will be the text that follows the underscore.
Example: To create a widget called Coil_Cooling the folder should be named as Widget_Coil_Cooling.
On – Contains the image used for the widget’s ‘On’ state.
Off – Contains the image used for the widget’s ‘Off’ state.
Optional folders can also be included in the 'Widget_' folder:
Alarm – Contains the image for the widget’s ‘Alarm’ overlay.
Override – Contains the image for the widget’s ‘Override’ overlay.
State – Contains a set of images that can be used to indicate multiple states or levels for Numeric or Enumerated datapoint values. This State folder contains a set of graphical images, each graphic defines the value range.
The graphic displayed for state or range is defined in the state.values file included in the State folder. This file maps a value or range to the required graphic. The file is a text file that can be created in a standard text editor (e.g. Notepad++). For example, to represent the different positions of a damper as below:
NOTE: This State folder does not support Boolean datapoint type
Relative Links