Please wait. Due to its content this page might take a while to load...
Please note that this topic will be updated soon with changes introduced with version 6. In the meantime, please refer to the support team if you have any questions.
Widget Designer version 4.5 introduces the feature to remote control nodes with so called "Node Commands". Up until now, commands were "only" for items like a Fader etc. but with the introduction of more advanced nodes, the need arose to control their features with commands too. These more complex nodes allow to enter advanced settings directly in the node and are able to execute functions themselves. Nodes that have remote controllable functions are for example:
- Projector Control Input node
- OptiTrack ID Tag Input node
- Watchfolder to PB Playlist Interaction node, etc.
Node commands are executed as any other command. It can be written, for example, in a Custom Script Button to be executed as soon as the button is pressed. Please refer to the chapter "Script Language" for more details about commands.
There are two ways to write a node command. One form is a more direct form whilst the other reminds of the structure of other common commands. As with all commands, the original form includes placeholders. By replacing them with according information the command addresses one particular setting from one particular node. So by typing the command, it assumes a definite shape.
As an example please see the table below. It shows the two basic command forms and examples how they could be filled out.
The Script Assist feature, offers the available functions for the according node:
- For the direct form: As soon as the dot behind the ID is typed...
- For the common form: As soon as the comma behind the ID is typed...
... , Script Assist looks up what this node is (e.g. a Projector Control) and displays the according commands in a list box. Use the arrow keys [Up] or [Down] to select an entry and press [Enter]. The [Esc] key hides the list box.
In addition to the purpose of controlling functions, node commands can also be used to assign a value to a parameter within a node. The examples refer to the depicted node chain.
Example for entering the Fader ID 5 into the Fader Output node:
The Fader Output node has the NodeID "3" as depicted in the upper left corner in the node. Its parameter for "Fader" is identified with "1" as depicted by the small superscript number next to the parameter field in the Node Properties dialog.
There are 3 possible command forms: (please note that the two direct forms do not support variables yet)
1) A direct node command
2) A 2nd direct node command
3) Common node command
Example for setting the "Input" source in the Delta Filter node to "Y Pos" from the Mouse Input node:
The Delta Filter node has the NodeID "2" and the Mouse Input node "1". Their IDs are depicted in the upper left corner in the node. The parameter for "Input" (that can accept input values from other nodes) is identified with "1" as depicted by the small superscript number next to the parameter field in the Node Properties dialog. The Mouse Input node provides several values, "Y Pos" is the second of them, thus it gets the ID "2".