Features

[atlasan]

I'm pushing new features. Let's check 'em before merging.

[atlasan]

This is it. I have to double check few things and eventually clean and optimize.

I'm proud of the Ancestors way: one could have a graph with the default node mode ON_REQUEST, every node is executed only when needed, being events what triggers the ancestors execution. The ON_REQUEST can be seamlessly mixed with the others modes, but only ancestors with that and ALWAYS mode will be updated (the others will continue to follow the old behaviours). This has been tested with the current nodes and seems working pretty good.

History is working quite good, some graph changes has to be verified (may save extra times or save before-after the actual action..). Anyway a perfect solution would consider which action and revert it, instead of saving the whole graph every time.

[ademola-lou]

Is there a plan to add a drop down option widget?

[atlasan]

Hi @waverider404. Not by me for now, but sure it would be useful. Do you have a coded solution?

[jagenjo]

@waverider404 there is already a dropdown widget called combo, when clicked displays all posible options in a context menu

[ademola-lou]

Oh that’s exactly what I needed thanks very much!