Detailed Description

The Node Container is used for node-based ui file tiling.

The target routing is configured in the cdpTargetRouting property and nodes are filtered based on the model types specified in the modelFilter property. The resulting nodes will load using the UI/form file specified in the uiFileName property. By default, they will be displayed as tiles in a flow-style layout. However, you can easily customize this layout by editing the childContainerName property and adding a container that aligns better with your preferences and needs.

Configuring the childContainerName property enables adding one of the following containers:

• The Flow Widget is already the default, but adding it to the Node Container allows editing all Flow Widget properties like margins and spacings.
• The Row is used when you want to show the tiles horizontally or vertically based on the window size.
• The Tab Widget shows the tiles on separate tab pages displaying the node names on the tab buttons.
• The Picture can be used to place nodes on pixel positions rather than container layouts. A typical use case is to make the picture show a map and load nodes on top of it at different locations. The UI/form file showing the nodes must be created using Picture or Picture Sequence as the form template. They both include properties for controlling the position and can be used as containers when needing to show more than just a picture.
• Other containers, like Group Box, Frame, and plain Widget can be added, but must contain a vertical or horizontal layout as explained in the childContainerName property details.

The loaded ui file can be based on any widget, but a RoutingContainer is often used to enable a temporary target routing while editing its relative routings. Target routing set on a top-level RoutingContainer will get replaced when loaded by the Node Container.

There is also a property, forceNodes, for hardcoding the nodes to load as ui tiles. This is useful when wanting a fixed subset of nodes from the cdpTargetRouting, or for testing the design within the CDP Studio Design mode.

The cdpTargetRouting can also be executed as a slot in runtime to load nodes from a different target.

See Creating a Dynamic GUI for Showing Dialogs for an example demonstrating how the Node Container can be used to load dialog buttons for controlling Sine components.