Nested View
The Nested View is a CygNet-aware container that shows another screen, meaning you can show a screen within another screen. This allows for more templated screens or dynamic screens, which can be swapped out at run-time based on user selection. The source file path for the nested view screen can be a local or network Windows file-system folder or a CygNet APPS or BSS folder. You can add as many nested views as you want to a single screen; you can also nest as many screens as you want within a nested view – there is no limit to the number of levels within each nested view.
Note: You can view a CygNet Studio screen (.csf) that is referenced in a nested View control, although the screen must be tabbed to display correctly.
A nested screen can inherit properties such as a facility or SiteService from its parent screen or have its own unique properties. A property set on a control on the parent screen, for example, a parent screen containing a button control where the facility is configured, can be passed down to any controls on the child nested screen. See To communicate between screens in a nested view via script for more information about sub-screen messaging and manipulation.
For example, you might have a parent screen containing several buttons each specifying a well facility, and then a nested screen containing a chart showing casing pressure and tubing pressure. By clicking each button, you can pass the associated well facility down to the chart and the data presented will change for each well. This may also include the live resolution of a relative facility, if the facility in the child screen is configured to resolve to a relative link.
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 nested view control supports property inheritance as a receiver of its SiteService and facility:
|
Self
Screen
|
Self
Screen
Other controls
|
none
|
none
|
The nested view control does not send its SiteService or facility to other controls.
Related Topics
