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

Re: [Web MIDI API] timeStamp and timestamp

From: Marcos Caceres <marcosscaceres@gmail.com>
Date: Sun, 16 Dec 2012 08:09:53 +0000
To: "public-audio@w3.org" <public-audio@w3.org>
Cc: Ms2ger <ms2ger@gmail.com>, Cameron McCormack <cam@mcc.id.au>
Message-ID: <AA5623D8BEEB4FD5B7B3E10B4692396E@gmail.com>
On Saturday, 15 December 2012 at 18:59, Marcos Caceres wrote:
> (Looping in Ms2ger and Cameron for guidance on DOM and WebIDL respectively…)
>  
> DOM4 Event defines:
> readonly attribute DOMTimeStamp timeStamp;
>  
>  
> While MIDIEvent [1] defines timestamp:  
> readonly attribute DOMHighResTimeStamp timestamp;
>  
> I think that is going to lead to confusion. Perhaps it might be worth talking to the WebIDL people and getting them to up the precision of DOMTimeStamp? Or easier to just rename the MIDIEvent attribute? Cameron, thoughts?  
>  
> Additionally, MIDIEvent defines a data attribute:
> readonly attribute Uint8Array data;
>  
> IIRC, there has also been talk of adding a 'data' attribute directly on the DOMEvent interface (with and any type). Not sure how far along that proposal has come along. Ms2ger, any idea?
Argh, seems I confused 'data' with 'detail' (from CustomEvent).. anyway, same thing.   
>  
>  
> [1] https://dvcs.w3.org/hg/audio/raw-file/tip/midi/specification.html#midievent-interface
> --  
> Marcos Caceres
> http://datadriven.com.au
Received on Sunday, 16 December 2012 08:10:23 UTC

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