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

Re: [web-audio-api] (setTargetValueAtTime): AudioParam.setTargetValueAtTime is misleading and underdefined (#152)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:30:03 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/152/24244577@github.com>
> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17334#6) by Olivier Thereaux on W3C Bugzilla. Thu, 23 Aug 2012 10:01:37 GMT

We had a lengthy conversation about this during the group's teleconference on 22nd August 2012:

There was agreement that the name was imperfect, but there was a compromise to be reached between using a nice, short method name and one that describes the behaviour of the method well. We discussed whether to remove the "at time", whether to remove "set", and so on.  

In the end, we reached the following proposed resolution:

* Change the setTargetValueAtTime method to setTargetAtTime
* The rest of the methods are a decent enough compromise, will be kept as is

Related changes were also proposed, which would make the description and behaviour of AudioParam automation easier to understand and use:

* Use startTime / endTime parameter names for AudioParam automation methods

* Setting audioparam value while there is an automation curve will cancel that automation curve and set value immediately

* Need a method to get a readonly reading of the combined value when using AudioParam automation curve

Reply to this email directly or view it on GitHub:
Received on Wednesday, 11 September 2013 14:31:31 UTC

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