W3C home > Mailing lists > Public > public-audio@w3.org > October to December 2012

Re: [Web MIDI API] MIDIEvent should have a port attribute

From: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Date: Mon, 24 Dec 2012 09:42:49 +0200
Message-ID: <CAJhzemU-i1OeAcMkAQe4_X6i_XOUJ7uU7BGgfnU7rfeu_NOG+Q@mail.gmail.com>
To: Marcos Caceres <w3c@marcosc.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
On Sun, Dec 23, 2012 at 10:35 PM, Marcos Caceres <w3c@marcosc.com> wrote:

>
>
> --
> Marcos Caceres
> http://datadriven.com.au
>
>
> On Sunday, 23 December 2012 at 20:34, Marcos Caceres wrote:
>
> > In situations where there are multiple sources attached to a device, it
> is important to distinguish which MIDI output emitted a particular message.
> As such, I recommend adding a port attribute to the MIDIEvent interface:
> >
> > interface MIDIPort : EventTarget {
> Whoops, I mean:
>
> interface MIDIEvent : Event {
> > readonly attribute MIDIPort port;
> > ...
> > }
>

Yes, actually I thought that for events on an EventTarget, both "this" and
".target" would automatically be the port, but now that I checked, it seems
that only the former is true. But that being the case, I think we should
use ".target", rather than introduce a new way of reporting the target.

Cheers,
Jussi
Received on Monday, 24 December 2012 07:43:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:04 UTC