W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2012

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

From: Chris Wilson <cwilso@google.com>
Date: Fri, 27 Jul 2012 10:39:20 -0700
Message-ID: <CAJK2wqVPBFpHZYXtU1EwP6pJdR+Fy5du3gzvXZ5ZDoDx0YFRpA@mail.gmail.com>
To: Peter van der Noord <peterdunord@gmail.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
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.  :)
Received on Friday, 27 July 2012 17:39:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 July 2012 17:39:49 GMT