- From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
- Date: Tue, 23 Oct 2012 16:30:03 +0300
- To: James Ingram <j.ingram@netcologne.de>
- Cc: public-audio@w3.org, Chris Wilson <cwilso@google.com>
Received on Tuesday, 23 October 2012 13:30:33 UTC
Hi James, On Tue, Oct 23, 2012 at 3:27 PM, James Ingram <j.ingram@netcologne.de>wrote: > Hi Chris, all, > > Congratulations on the First Public Working Draft of the Web MIDI API. > Looks good to me, but I have a question: > > Does adding an extra ECMAScript attribute to a MIDIMessage cause any > problems for the underlying system? I've tried to find the answer to this > question in the referenced documents, but without success. > If I understand you correctly, you mean like: var msg = {data: new Uint8Array([...])} msg.customStuff = "stuff" // Do something with the msg, and eventually send it output.send(msg) In that case, no. The parsing of a WebIDL `dictionary` (MIDIMessage is specified as one) works by extracting only the meaningful data (as in the specified properties) out of the JS (or other) object it's given. If you someday hit an implementation of the Web MIDI API where there are adverse effects for this, you probably have to file a bug against that implementation. ;) > In my current, working (Jazz plug-in) application [1], some MIDIMessages > are given an extra attribute, without producing any adverse effects, but > I'd like to be sure that this is okay in the Web MIDI API as well. Cheers, Jussi > All the best, > James >
Received on Tuesday, 23 October 2012 13:30:33 UTC