Image

The Image control is a CygNet-aware tool that can be used to display images on your screens. Supported image file formats include scalable vector graphics (.svg), bitmap (.bmp), portable network graphics (.png), jpeg (.jpg and .jpeg), and graphics interchange format (.gif). The image can be configured to display a default static image or a dynamic image that changes based on the point state or the alarm condition of the associated point. The control can be configured with a valid point configuration but prevented from retrieving any CygNet data, allowing the display of static text while still allowing CygNet data context available from script. Date, time, and value formatting for the text displayed on the control is supported. The control can be hidden if the associated point is invalid. The mouse cursor that appears when the mouse hovers over the control is configurable. Font sizing, text styling, and text weighting are also configurable. This control supports tooltips, which can be displayed as tokenized text, a Canvas object, or the tooltip can be scripted to retrieve and display values for related points or CygNet notes. 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. The image control does not support animated .gifs, or animated .svgs, at this time. If no default or custom point state image is specified, a missing image icon () is displayed at design and run mode.

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 image control supports property inheritance as a receiver of its SiteService and facility:

The image control does not send its SiteService or facility to other controls.

Related Topics