[Bug 20512] MIDIEvent lacking constructor

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

--- Comment #4 from Chris Wilson <cwilso@gmail.com> ---
(In reply to comment #3)
> (In reply to comment #1)
> > Why should you ever need to construct a MIDIEvent?
> 
> Because you are writing a sequencer, auto-chord maker, arpeggiator, etc?

That's a great reason why you should need to maintain MIDI event data - but not
really a justification for why you would want to create an Event-derived object
that contains said data.  This isn't just a data container - it has all the
Event stuff, too - and it's no longer used for sending data.  (For an
arpeggiator, for example, you'd just create the data array for each note and
call send().)

Marcos' "primarily for testing, firing synthetic events" is a justifiable
reason, I suppose; however, I'm not sure I see how this is done in other specs.
 Is there a TouchEvent constructor somewhere?

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

Received on Tuesday, 8 January 2013 17:46:06 UTC