[Bug 19975] Promote data and timestamp onmessage/MIDIEvent, get rid of MIDIMessage altogether?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=19975

--- Comment #13 from Jussi Kalliokoski <jussi.kalliokoski@gmail.com> ---
(In reply to comment #12)
> Still, it's quite an advanced usage, I'd say. Rather than cluttering up all
> webmidi receivers, we could provide a method in MIDIInput like
> "getQueuedMessageCount" which tells you if there are still messages
> immediately following the current one. Now the basic webmidi receivers will
> not use it and benefit from the simplifications proposed by Chris. And the
> advanced applications can cache all queued messages until there are no
> queued messages anymore, and then process them at once, possibly eliminating
> redundant or outdated messages.
> 
> Would that be a solution?

Or, as Chris suggested, we could go with the simplified single message proposal
for now, and consider adding an additional event handler called "onmessages" to
a future version, letting the developer choose the tradeoff.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 3 December 2012 21:50:47 UTC