Use Page nodes to create the structure of an application user interface. For example, you can create different parts of the user interface, such as Home, Media Browser, Navigation, or Settings screens, each in their own hierarchy of Page nodes.

Activating Page nodes When a Page node is active all its ancestor Page and PageHost nodes are active too. When a Page or a PageHost node is active all its content and content of all its ancestor Page and PageHost nodes is visible and users can interact with it. In a simple use case only one Page node in a hierarchy is active. However, you can build a complex structure by activating more than one Page or PageHost node in a hierarchy at the same time. To achieve this set the auto-activate flag on all Page and PageHost nodes which you want to automatically activate. Such nodes become automatically active when their parent Page or PageHost node is active.

Navigating between Page nodes PageHost nodes handle the navigation and transitions between Page nodes. For this reason you must place a PageHost node as an ancestor of a Page node tree hierarchy. To navigate between Page nodes request the navigation system to navigate to the selected page. When you navigate to a Page node, Kanzi transitions the node to a visible (activated) state and the contents of the node become visible to the user. When you navigate away from a Page node, Kanzi transitions the node to an invisible (deactivated) state and the contents of the node are no longer visible to the user. Kanzi supports both animated (over-time) and instant (immediate) transitions between Page nodes.

Inherits properties and message types from PageMetadata.

Page.Page:create(name) ¶

Creates a Page node.

Deprecated In Kanzi 4.0.0. Pages are deprecated, use Activity2D and ExclusiveActivityHost2D instead.

Parameters

name

(string)

The name of the node.

Return Values

(Page)

The created node.