This is a list of values that are passed into the function. FunctionArguments have to be supplied in the same order as the inputs to a function. Even if there are just one or even no inputs, the list still needs to be contained in double curly brackets. The values must also be of the same type as the function's arguments.

When GenerativeComponents's dependency analyzer considers a node that is using the ByFunction technique, the analyzer looks only at the node's FunctionArguments property. The analyzer does not look into the body of the function, itself.

Therefore, if a function references other top-level nodes, you should not simply use those node names directly in their function body. If this is done, the dependency analyzer won't 'see' those names, and won't make any dynamic links to those nodes.

Rather, the function header should be revised so that it takes an argument for each of those other top-level nodes, and use those argument names in your function body. The actual top-level nodes should then be listed in the FunctionArguments property.

The first argument has special significance in the ByFunction technique. This determines in which model space the node is drawn. It is always drawn in the same model as the first argument.