CygNet Grid

The CygNet Grid is a CygNet-aware control that supports the creation of customizable and interactive tables for the display and management of large amounts of data in columns and rows. Four customizable column types are supported: Facility, Generic, History, and Point: facility columns are mapped to a facility attribute and can resolve to a relative facility; generic columns can display any kind of scripted data of your choice and its cells can be edited in run mode; history columns are used to add a sparkline chart in each cell for a specified UDC; point columns are mapped to a UDC and point attribute and the color can be explicitly configured or sourced from the point state color defined for the point represented in the row. The facility and SiteService are configured for the grid row and each can be explicitly set (and filtered) or sourced from other another control or the screen. Any column's background, text, and border color can be explicitly configured or sourced from the point state color defined for the associated point. Colors in the control can be overridden when a custom color palette is selected for the screen. Alarm indication (blinking) is supported for a point column's background, text, and border when the associated point is in alarm. A context menu is available 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. Each cell in a CygNet grid is like a text tool and the two controls share many color and point configuration properties.

A CygNet grid can be used to display any kind of data, not just data from CygNet, although it can only be run on a system running active CygNet services. The columns represent data from a current value service; the rows represent facilities. The grid can be configured to show any attribute of a point (configuration, current value, facility information). Other applications might include the display of a list of non-telemetered facilities with user-editable cells for manual data entry, or interaction with a list of configuration files.

For example, you could have one set of columns configured to show CygNet data (UDCs, point attributes, facility attributes), and another set of columns where you might script the contents. See Configuring the CygNet Grid Control for more information.

Property Inheritance

Property Inheritance

Property inheritance is a widely used concept in Canvas. The application supports an explicit relationship between screens, objects, and controls, where certain property values, such as SiteService and facility tags, 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 SiteService and facility. Depending on how you have your screens, objects, and controls set up, the SiteService and facility may come from any one of the following sources:

• from itself — indicated by selecting <Self> and then explicitly configuring the property
• inherited from the screen — indicated by selecting Screen, which is always present as a sender
• inherited from another control — indicated by selecting the Name of the sending control

Broadcasting

Screens and objects support an additional notification option to broadcast their SiteService and facility selection changes to other open screens running in the Canvas or Canvas View application. If configured, a <Broadcast> option is available to source the screen's SiteService and facility 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 CygNet grid control supports property inheritance as a receiver of its SiteService and facility, and as a sender of its facility:

The CygNet grid is multi-facility aware and depending on the level of a configured hierarchy selected (from an associated tag chooser) will depend on how many rows will be loaded into the associated grid.

Related Topics