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

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

From: Marcos Caceres <w3c@marcosc.com>
Date: Mon, 24 Dec 2012 09:04:22 +0000
To: Jussi Kalliokoski <jussi.kalliokoski@gmail.com>
Cc: "public-audio@w3.org" <public-audio@w3.org>
Message-ID: <A32AC853054E4684BA4319C0AB970F4A@marcosc.com>


On Monday, 24 December 2012 at 07:42, Jussi Kalliokoski wrote:

> On Sun, Dec 23, 2012 at 10:35 PM, Marcos Caceres <w3c@marcosc.com (mailto:w3c@marcosc.com)> wrote:
> > 
> > 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.
> 

Moving discussion to:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20502

-- 
Marcos Caceres
http://datadriven.com.au
Received on Monday, 24 December 2012 09:04:55 UTC

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