The api for an ambient light. An ambient light can be created by calling the addAmbientLight method.
Definition of the event response mapping for interaction events. This mapping is used to map the event type to the corresponding event interface.
Type declaration for a filter pattern used to hierarchically filter nodes of the scene tree by name.
Dictionary type declaration for filter patterns used to filter nodes of the scene tree by name. The dictionary keys correspond to the IDs of outputs of a ShapeDiver model. The dictionary values are arrays of patterns for hierarchical matching of node names of the output. Each pattern is defined by an array of strings, which represent regular expressions that are applied to nodes of the hierarchy.
Example (simplified, disregarding the regular expression syntax):
{
"OUTPUT_ID": [
["Node_a", "Node_b"], // matches nodes with the name "Node_a.Node_b" in the output with the ID "OUTPUT_ID"
["Node_a", "Node_c"], // matches nodes with the name "Node_a.Node_c" in the output with the ID "OUTPUT_ID"
["Node_a", "Node_d", "Node_e"] // matches nodes with the name "Node_a.Node_d.Node_e" in the output with the ID "OUTPUT_ID"
]
}
The activation key of the restriction. If the key is not provided, no key is assigned. If the key is provided, the restriction is only active when the key is pressed.
If the restriction should be enabled by default.
If the enabling or disabling of the restriction is allowed to the end user. If it is not editable, the default value for enabling or disabling the restriction is used.
Priority of the restriction. The higher the priority, the sooner the restriction is applied. If the priority is the same, the result that is closer to the original point is chosen.
Add interaction data to the node.
If the node already has interaction data, the function will remove the interaction data and add the new interaction data. Then the function will update the version of the node.
This function checks if the name of the node matches the given name. The name is provided without the display component in the beginning. It is assumed that the node is in the correct display component.
Convert the user-defined name-filters to filter patterns as used by useNodeInteractionData.
The name filter is an array of dot-separated strings. Each string represents a pattern to hierarchically match node names. The first part of the pattern is the output name. The rest of the pattern correspond to hierarchical node names, which may contain the "*" character as a wildcard to match any node name or any part of the node name.
The user-defined name filters to convert.
A mapping of output IDs to output names for the session to be used.
The filter pattern object to be used with useNodeInteractionData, useSelection, and other interaction hooks.
Convert the user-defined name-filters to filter patterns as used by useNodeInteractionData.
The name filter is an array of dot-separated strings. Each string represents a pattern to hierarchically match node names. The first part of the pattern is the instance ID. The rest of the pattern correspond to hierarchical node names, which may contain the "*" character as a wildcard to match any node name or any part of the node name.
The user-defined name filters to convert.
The IDs of the instances to be used.
The filter pattern object to be used with useNodeInteractionData, useSelection, and other interaction hooks.
Recurse the scene tree downwards starting from the given node, gather all nodes that match the pattern, and add them to the result array.
The node to start traversing from. Typically this is the node of an output of a ShapeDiver model.
The hierarchical pattern to check for. Each string of the pattern represents a regular expression for matching the node name.
The name of the output API to be used for the concatenated node name.
The result object, matching nodes will be added here.
The current index into the pattern array.
Traverse the node hierarchy upwards to find the node that corresponds to an instance node. Return the instance id, and the original names concatenated using dots.
We know that it is an instance node if it has a session API data in its parent. We return the instanceId as the outputId to be used in the other functions.
Traverse the node hierarchy upwards to find the node that corresponds to an output of the ShapeDiver model. Return the node itself, the corresponding output id and name, and the original names concatenated using dots.
The node to start the upwards traversal from.
Get the name of the node. If the node has a ChunkData, return the name of the ChunkData. If strictNaming is true, return the original name of the node. If strictNaming is false, return the original name if it exists, otherwise return the name of the node.
Get the nodes within the session API by their names.
The names of the nodes.
Try to match the given nodes with the patterns. For matching nodes, return the concatenated names of the nodes as required for setting values of interaction parameters.
The patterns to match the node names.
The nodes to process.
The concatenated names of the nodes that match the pattern.
Properties for the grid restriction