[Quest] Simpler way to reset a ProcessNode state

[mhusinsky]

original question on element

tl;dr

Should there be an shorter way to reset a ProcessNode's state (i.e. calling create and subsequently update again, similar to what alt+rightclick did on subpatches in beta)? right now there is only the ManageProcess region to do that, which is laborious to create (in beta it was just a click - in gamma i miss this simplicity. it takes quite a lot of clicks to: create the region, move the processnode inside, connect everything, create the bool iobox, and reconfigure it to bang).

one option could be a hidden boolean "reset" pin, that can be configured to be shown, similar to "apply".

here's my thinking why this could improve UX, especially for new users

For beginners, the ProcessNode is probably the first "type" they get to know. From my experience the allways-running scheme of VVVV invites to start patching and play around while the node-graph grows. at some point, one needs to clean-up and optimize for reusability of nodes - in beta this would be subpatches, in gamma processnodes are the first option to achieve this.

very often, as a next step, some initial state (that might be different for various instances of the processnode) needs to be taken care of - a great possibilty to introduce the create operation (and with it, operations in general). in create, some values are written to a pad and these are further modified in update. however, when one needs to reset the node, one has to do one of the following:

• in the processnode: implement some logic for a reset on update, e.g. an if-region with logic that resets the pad values etc. - probably very similar or equal stuff that is already on create -> blows up the patch
• use the ManageProcess region, which takes quite some clicks to be ready to use (see above)
• [probably some other options that i missed]

both options above feel over-the-top for just resetting the state of the node, as the create-operation might have allready all that is needed logic-wise, there is just no quick way to reset the node.

for advanced users this is probably a non-issue, as for records or classes each operation can be called individually. Processnodes however do not offer the option to call "create" again. a shortcut to do that would be very useful (and as a side-effect one could give a first introduction to operations).

[mhusinsky]

well, right after finishing this post i had a look at a simple processnode with a reset pin - the LFO and found out that actually there is a possibility to have a quick boolean "reset" pin by just creating an operation called "reset". this now can be configured like an "apply" pin and it might solve parts of the problem. still, logic for create and reset might have to be duplicated.

i leave this open for discussion though - at least for a discussion whether alt+rightclick should do a reset or not.

[edit: formulation]

[gregsn]

Sorry, @mhusinsky for the delayed response... #45