Page system
A Page is a reusable node tree that never renders on its own. Define it inResources and use it as the Content of layouts, Dialog, TabItem, or List.
Define a Page
Resource Type="Page"requiresName.- Page content is a normal node tree and can contain layouts, controls, Data, Tabs, Lists, and so on.
- Pages do not render automatically; they enter the UI only when referenced by
Content. - Page content shares the consumer’s scope:
Inputs,Data,Results, andSize.
Reference a Page
Both forms are equivalent:Content and inline children are mutually exclusive:
Content containers
Nesting and limits
- A Page may reference another Page through
Content. - Missing Pages and
A→B→Acycles are rejected. - Pages still count toward XML depth, element count, and nesting limits.
Targetin a Page is still widget-level; avoid relying on duplicate Targets when the same Page is used multiple times.