This then can be used as string argument to some dynamic node and its custom properties used for variables (with _ stripped). However this might increase complexity, so a better option might be to separate loading such strings as node block and for user-compound node just use the block itself. It will require some other method of binding variables though..
One option would be use Placeholder node which takes variable name as argument and returns {} of appropriate type, but is bound to real argument by user-compound node mechanism.
Example:
Sine-pulsating circle with pos, min/max radiuses and period as arguments
```
CirclePR(
position = position,
radius = min_radius +
(max_radius-min_radius) * 0.5 * (1+Sin(Linear(speed=1/period)))
)
```
This then can be used as string argument to some dynamic node and its custom properties used for variables (with _ stripped). However this might increase complexity, so a better option might be to separate loading such strings as node block and for user-compound node just use the block itself. It will require some other method of binding variables though..
One option would be use `Placeholder` node which takes variable name as argument and returns `{}` of appropriate type, but is bound to real argument by user-compound node mechanism.
Example:
Sine-pulsating circle with pos, min/max radiuses and period as arguments
This then can be used as string argument to some dynamic node and its custom properties used for variables (with _ stripped). However this might increase complexity, so a better option might be to separate loading such strings as node block and for user-compound node just use the block itself. It will require some other method of binding variables though..
One option would be use
Placeholdernode which takes variable name as argument and returns{}of appropriate type, but is bound to real argument by user-compound node mechanism.Well, this will be implemented directly and straightforwardly with rainynite-linaer. NO MORE WHEEL INVENTING