Copy node, keep output bindings

[lerou]

Hi,

When you copy a node, you can keep its bindings. That's a very good help! But it only works for inputs.

I know, this would not work for all outputs, since they often have a 1:1 binding (for instance output float to float expression). But it would be awesome to see this feature for those outputs that have a n:1 binding. Best example: You have a node that fires an event. That event is bound to a script. Now you copy that node 100 times and want all fired events to be bound to the same script method. If you don't have an intern who you can force to manually bind those events, you're screwed.

Having this would be great! Or is there a way to do this that I don't know?

Thanks,
rou

[lerou]

Thought for a moment I had a workaround. Using an event in the scene data. So inside the interface container I would bind an outgoing event to trigger the scene event. Then outside the container I would get my event not directly from an output of the interface container, but from the scene event. This works so far.

But then I copied the container and saw that the binding was gone. Why?! That would have been a real good use for the scene data.

So, who's gonna make all those bindings for me? Anyone? No? Hm.

cheers,
rou

[joysprod]

Could you fire the event by OSC, therefore not requiring a physical connection?

Peter

[lerou]

Yes, that would be a workaround. However I don't want to use a network protocol for such a basic functionality.

thanks,
rou

[chriss0212]

i agree with peter....

thats the way i do it in most cases .....but i agree with rou

greetz

christian

[lerou]

Yeah, I agree that's probably the best workaround atm

However one thing I like about Ventuz is that it does not have invisible connections. I've seen quite a few applications that have exactly that problem: you don't see connections. Some nodes are connected by putting in another node's name in the property editor. That's a terrible design. Ventuz shows your connections. Sometimes it gets messy, but I still prefer that over any invisible connection. Using OSC introduces invisible connections. I don't like that. Nobody will be able to understand the scene without digging into each container.

So please please please: support copying outgoing event connections. Thanks!
rou

[chriss0212]

+1