When setting up a new object I lose productivity switching between the inner and outer context.
For example my current flow is:
- I am patching in OuterProcess and I decide I need an InnerProcess. Ideally I would take advantage of vvvv real-time context and have real working data I can see in the tooltips and results as soon as possible.
- I switch context to the patch definition to create InnerProcess definition
- I go back into OuterProcess context and instantiate an InnerProcess node
- I go into the InnerProcess and create some inputs and outputs and possibly type them
- I go back to the OuterProcess and connect the inputs and outputs.
- I now go into the InnerProcess and am ready to patch with real data
When implementing interfaces I have to switch context to the interface itself to check the names of inputs and outputs, costing time and mental focus.
This has two parts
Propose from an outside context you can force add an input or an output to a node by Space+Click on the body of the node while creating a link.
Propose In the nodebrowser a new switch that shows local inputs and outputs for this node context.
- They should appear at the top of the node browser list if this is enabled.
- Inputs and Outputs will have a color highlight if they ‘should’ exist but don’t, either due to being plugged into the outer context of the node or because they should exist on an interface operation.
- The inputs and outputs show the Member Operation they are on in brackets eg World (SetWorld) or Value (Update).
- If those member operations already exist in the node they should be colored same as they are on the node.
- If the member operation doesn’t exist on the node then creating the input pin from the node browser also creates the member operation
This will enable users to switch context less often when setting up objects or interfaces.
For the object case you can force connect all your pins to the premature object and then switch to the inside context one time and access those as ‘should’ be connected pins.
For the interface case you have the input and output names and member operations in the node browser and don’t need to switch to the Interface context to check them.