W3C home > Mailing lists > Public > public-audio@w3.org > April to June 2013

WaveShaperNode.curve issues

From: Robert O'Callahan <robert@ocallahan.org>
Date: Mon, 6 May 2013 18:52:28 +1200
Message-ID: <CAOp6jLbvFqHJfsvez-G4D-VRJYGrwfnZBztMaACfxw3ZVhhmAg@mail.gmail.com>
To: "public-audio@w3.org" <public-audio@w3.org>
1) Scripts can modify the content of the array at any time and it's not
clear when those changes take effect.
2) This is especially acute when script can actually replace the "curve"
array with a different JS array altogether (at any time).
3) What if the array is empty?
4) What if it contains infinities or NaNs?

We could avoid all these problems by changing from "curve" to a method
"setCurve(Float32Array)" that throws if the array is empty or contains
non-finite values, and neuters the array so that no copy is required but JS
can't modify the data anymore. But can we do that, or are we forced to
support this for compatibility?

Rob
-- 
q“qIqfq qyqoquq qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qyqoquq,q qwqhqaqtq
qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq qsqiqnqnqeqrqsq
qlqoqvqeq qtqhqoqsqeq qwqhqoq qlqoqvqeq qtqhqeqmq.q qAqnqdq qiqfq qyqoquq
qdqoq qgqoqoqdq qtqoq qtqhqoqsqeq qwqhqoq qaqrqeq qgqoqoqdq qtqoq qyqoquq,q
qwqhqaqtq qcqrqeqdqiqtq qiqsq qtqhqaqtq qtqoq qyqoquq?q qEqvqeqnq
qsqiqnqnqeqrqsq qdqoq qtqhqaqtq.q"
Received on Monday, 6 May 2013 06:52:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:18 UTC