Javi Agenjo
Javi Agenjo
I guess thats a bug from edge, the current function relies on clientY and getClientBoundingRect which are well defined functions in the standard, so if some weird thing happens in...
I will check it
which one? when it says "rename slot" and "remove slot" ?
yes, because first you receive the deselection, and after that the selection of the new item
Yes, this is a problem of the current architecture. Nodes onExecute is executed constantly (when the runStep method is called for the graph), but onAction is executed when the event...
I will research on the topic this week, I could create a function that executes from Node triggering the event to the node receiving the event. Ask me about it...
> Its unfortunate that the flow separates. I would have assumed getInputData would have forced a fetch if required, but I suppose there is no easy way to do that....
The subgraph is full of bugs (mostly because the implementation is a little bit messy and I never had the time to test all use-cases). I will give it a...
you can use the Events system to trigger nodes once you end an async task but then you won't be able to take advantage of the nodes pool as all...
it is an interesting idea, I will consider it in a future update.