Closed wargreen closed 2 months ago
Hi @wargreen . Thanks for your request and pointing this out.
The problem here is that "OSCExecute" is an output with a somewhat unusual name. Unfortunately it's not easily recognizable as an output node. I will look into that and improve the design.
I adjusted the design of output node to make this a little bit more evident:
Thank you for this ! I can't check it now : does all the input / output have the same design ? I don't remember but it can be really cool.
Not not yet. But it's a great idea. I will look into it.
Describe the bug When opening the example of OscOutput, we can see that the graph is driven by the symbol OSCExecute. This symbol don't seem to really exist : no parameters and can't find it for add it elsewhere.
Please complete the following information):
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and reproducible example :)
Screenshots
Additional context Also tried on windows.