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 runtime based on user selection. 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: In the Canvas Native view you can referenced a CygNet Studio screen (.csf) in a Nested View control, although the screen must be tabbed to display correctly. CygNet Studio screens (.csf) are not supported in a Nested View in the CygNet TWC web view.
This control is supported in the Canvas Native view and the CygNet TWC web view.
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, 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 Nested View control supports property inheritance as a receiver of its SiteService and facility:
| Receive from | Send to | ||
|---|---|---|---|
| SiteService | Facility | SiteService | Facility |
| self screen |
self screen other controls |
none | none |
The Nested View control does not send its SiteService or facility to other controls.
