- From: Peter van der Noord <peterdunord@gmail.com>
- Date: Mon, 16 Jul 2012 14:52:11 +0200
- To: "public-audio@w3.org" <public-audio@w3.org>
I agree on this one, the disconnecting implementation is quite unhandy. When i want to remove a node from the graph, i have to (if i understand the api correctly) - iterate through all outputs of the node and disconnect them (doable) - check every connection in the graph if it has a connection to either an input or a parameter of the module, and disconnect the output that leads to it (thus also potentially disconnecting connections that dont lead to said module). This is cumbersome, especially when there's no feedback to retrieve about the current state of the graph for debugging. In my humble opinion: - there should be a method to remove a module from the context (and obviously clearing all connections) - there should be a way to get the connections from an input or output - there should be a way to remove a single connection (by supplying a connection) Peter
Received on Monday, 16 July 2012 12:52:49 UTC