Re: [Bug 17793] New: AudioNode.disconnect() needs to be able to disconnect only one connection

On Sat, Jul 21, 2012 at 3:21 AM, Peter van der Noord
<peterdunord@gmail.com>wrote:

> Ok. What is the "derived class nodes issue"?
>

What you'd mentioned - that you can't really override an AudioNode
directly, so that normalAudioNode.connect( myCompositeNode) would work.
 You can expose an input and output node to connect to, of course.


> But that question i asked:
>
> > how do you see it, would that latest disconnect refinement be enough?
> (not looking at the params disconnecting issue...)
>
> Don't get me wrong, i'm not suggesting removing those methods, i am aware
>> that they are fully necessary for other types of applications than mine. I
>> was hoping for an addition that could offer those functionalities by other
>> means as well.
>>
>
> I think they're mostly there, except for needing to build a "composite"
> node.
>
> Is that regarding the example you gave with the clockdivider? Because i
> still don't quite understand what you meant there.
>

Yes.  I meant that multiple inputs and outputs that are semantic-free; for
a node where you want semantics attached ("this is the 8x signal"), you
might want to name them.

Sorry about the lag in response, BTW - I'm on vacation now.  :)