onExecute returning promise about litegraph.js HOT 3 CLOSED

Hi,

Technically yes, thats the function that iterates through every node calling the onExecute on them.
But what I do not understand is why you want something that is not asyncronous to be asynchronous when onExecute methods are not depending on external stuff.

I mean, you can wrap it if you want, but it is still a sync code called from an async wrapper.

The only use case I can imagine is if one node relies on some async actions, but in that case it will be harder that wrapping onExecute, you will need to call onExecute on the next node after the async onExecute of this node finishes, and that would take some time to code. I guess you can create a runStepAsync that handles promises in some sort of onExecuteAsync per node, but then you will have to handle which nodes are sync and which ones aren't.

Tell me more about your use-case

from litegraph.js.

That's exactly what I'm going for.
I want to use litegraph in a different way (nonrealtime) than it's currently designed.
About the usecase, i want to configure a node with an url, so it can fetch an url during onExecute.
I'm going to see if i can get a runStepAsync going.
It's very easy to distinguish between async & sync onExecute-functions, as i only have to check the type of their output (promise or not).

from litegraph.js.

Well, I though about it too some time ago, and my approach was more focused in events, similar to how UDK4 Blueprints work, where a node can dispatch an event, and you can wire events between boxes.

The current approach is more for signal processing (take one input, process it, generate output).

LiteGraph currently supports events, it is not well documented, but the feature is there. The idea is that you can declare event inputs/outputs and connect them, and from a node you can dispatch them using the method trigger. This will execute independently of runStep.

Let me know your advances.

from litegraph.js.