Keyboard events are not properly translated to on/off events

[GoogleCodeExporter]

What steps will reproduce the problem?
1.  Press a key on the keyboard
2.  Press another key without releasing the first
3.  Release the first key

What is the expected output? 

The first note should sound at 1.  It should transition to the second at 2.
 At event 3, the second note should keep sounding until that key is released.

What do you see instead?

The first note sounds.  The second note sounds as long as the first key is
depressed.  When the first key is released the second note stops.

What version of the product are you using? On what operating system?

Current version on iPhone as of March 8.

Please provide any additional information below.

There may be difficulties handling this with the way the API sends
multitouch info, but other apps have resolved the issue.  I believe that
noise.io had a similar problem when it was released and it was resolved.

Original issue reported on code.google.com by ctglea...@gmail.com on 8 Mar 2009 at 3:47

[GoogleCodeExporter]

Original comment by allen.po...@gmail.com on 9 Mar 2009 at 3:28

• Changed state: Accepted
• Added labels: Priority-High
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Original comment by allen.po...@gmail.com on 15 Mar 2009 at 7:08

[GoogleCodeExporter]

Thanks for the bug report. Should be fixed as of r63.  Please re-open if you 
still find any issues.

The API does indeed send on/off events for each independent touch, but it seems 
to be flaky.  I found when 
pressing a lot randomly I would get ON events, but not corresponding off 
events.  Therefore, there is a hard 
coded workaround to remove all events when there are no fingers pressed.

Original comment by allen.po...@gmail.com on 16 Mar 2009 at 4:21

• Changed state: Fixed