useful design's picture
+0

Sorry if this has already been answered in a general sense somewhere else but I didn't find anything.

I have a simple set of nodes that splits a list of 2D points into individual data points and passes each one through it's own Smooth with Inertia node. Then recombines each data point into a 2D Point list the same length as the one that came in.

Feeding it unit test data in the same composition it works fine, and I'm using it in another much larger composition. But as soon as I make it a sub-composition and feed the unit test data into the sub-comp node it outputs a list of null data (same number of 2D Point elements but all (0, 0) in value).

sub-comp for smoothing a list in working state.vuo

Smooth List test rig.vuo

The sub composition used in the above test rig: useful design.smoothListWithInertia.vuo

Comments

One thing making this made me

useful design's picture
Submitted by

One thing making this made me realise, when you make a sub composition for smoothing you necessarily don't want to have to commit the data-type of the nodes within it.

Keeping it generic would allow it to be used for as many datatype as the Smooth with Inertia patch can accept. But it's not possible to make the sub comp without hardwiring a datatype into the composition, in this case 2D point. If possible it would be ideal if the sub composition could accept a list of n–dimensional points or colours etc. I'm not sure if a future Vuo could do that?

1 Answer

jstrecker's picture
+0

The answer to this (and the fact that we're changing it to be more intuitive) lies in the feature request Change subcomposition event behavior — an event into a published input comes in just through that input, not all inputs.