The Tile View is a CygNet-aware container that displays real-time data in a series of tiled Detail controls, one for each facility provided. The Tile View determines how many Detail tiles to draw based on facility inheritance, and then fills itself in with a tile for each child of the parent facility, adjusting layout accordingly. The Tile View allows you to build screens in a dynamic way with little maintenance, and easily add new points or facilities to a screen without additional scripting. Each Detail tile in a Tile View displays six elements:
| 1. – 3. | three tokenized text strings (top, middle and bottom). The control can display a static text string, such as a label, legend, tooltip, or a dynamic text string based on point or facility attributes. Dynamic text is built using tokens, which can represent real-time CVS point properties, point configuration properties, and facility properties. In run mode, the tokens are replaced with the attribute's value. | |
| 4. | an alarm icon that can be configured to change color based on point state and change image based on alarm priority | |
| 5. | a small sparkline with configurable line color, x- and y-axis, date ranges, both relative and absolute, and live data updates | |
| 6. | an arrow that is scripted to flip the Detail control when clicked and display an object of your choosing on the reverse side of the Detail control. The object on the reverse side will receive its point configuration from the Detail control. |
The last three elements (alarm icon, sparkline, and flip icon) can be toggled on or off. The control's color elements can be set to one of the following options: a) automatically follow the selected application theme regardless of the underlying color palette used, b) sourced from the point state color defined for the associated point, or c) be explicitly configured. (The sparkline's color is not theme specific.) Colors displayed in the control can be overridden when a custom color palette is selected for the screen. The Tile View has two display modes for its tiles:
- Single UDC — Where data for a single UDC is displayed and a tile will be created for each child of a parent facility
- Each UDC for Facility — Where facilities are queried for their associated UDCs and a tile will be created for each one
Additionally, each tile in the Tile View includes a title bar showing the facility name and a maximize button. When clicked in run mode the tile will maximize and open a screen, object, or CygNet Studio screen populated with related data for the passed-in facility from the originating tile. The maximized screen or object can be minimized to return to the initial Tile View. Each tile displays a context menu in run mode with access to CygNet point and alarm data, including alarm acknowledgment, current and history values, point and facility configuration, and trending point data on a default chart.
Tile View Example
The following image shows a Tag Chooser and a Tile View control.
|
Sample Tile View Control |
Property Inheritance
Property Inheritance
Property inheritance, or sending and receiving, is a widely used concept in Canvas. The application supports an explicit relationship between screens, objects, and controls, where certain property values, such as facilities and SiteService details, are passed from one element to another via an inheritance framework. Screens, objects, and controls can be configured as property senders or property receivers and provide configuration options where you can explicitly define the source of the facility and SiteService. Depending on how you have your screens, objects, and controls configured, the facility and SiteService may be received from any one of the following sources:
- from itself — indicated by selecting <Self> and then explicitly configuring the property
- received from the screen — indicated by selecting Screen, which is always present as a sender
- received from another control — indicated by selecting the Name of the sending control.
Broadcasting
Screens and objects support an additional notification option to broadcast their facility and SiteService selection changes to other open screens. If configured, a <Broadcast> option is available to source the screen's facility and SiteService properties from another open screen.
For example, a Text Tool can be configured to get its facility from the screen and the screen can be configured to get its facility from a Tag Chooser. Or Screen_A might source its facility from Screen_B, which gets its facility from a Tag Chooser.
Receiver or Sender
The Tile View control supports property inheritance as a receiver of its SiteService and facility:
| Receive from | Send to | ||
|---|---|---|---|
| SiteService | Facility | SiteService | Facility |
| none | self screen other controls |
none | none |
The Tile View does not send its SiteService or facility to other controls.
