"Alt" is sticky in ConnectBot

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Run ConnectBot, start a program that uses Alt-modifiers (I used irssi for 
this example)
2. Press and release the Alt key
3. Type a number (e.g. 2).  Note that irssi switches to window 2.
4. Type another number (e.g. 1).  Note that irssi switches to window 1.

I can reproduce this consistently, every time.

What is the expected output? What do you see instead?
I expect the Alt to be released after step 3, such that a literal "1" gets 
inserted into the text field in step 4.

What version of the product are you using? On what operating system?
Hacker's Keyboard v1.20
Samsung Galaxy Tab 10.1, Android 3.1
ConnectBot 1.7.1

Please provide any additional information below.

I don't know if this is a bug in the Hacker's Keyboard or a bug in ConnectBot, 
as I don't have any other apps that use Alt to test with.

I suspect it's a keyboard bug because if I press-and-hold Alt, then type a 
number, then release Alt, I get the expected behavior -- that is, typing 
subsequent keys send literal characters, rather than Alt+char.

Original issue reported on code.google.com by des.siam...@gmail.com on 8 Jul 2011 at 7:13

[GoogleCodeExporter]

I'm pretty sure this is a feature. Try to use emacs without it.

Original comment by belg4...@gmail.com on 12 Jul 2011 at 12:28

[GoogleCodeExporter]

Actually I do use emacs inside ConnectBot, and it bugs the $NAUGHTY_WORD out of 
me. :)  M-x foo always requires an extra keystroke (unless I try to multi-touch 
it, and my fingers are just a little too big for that), and there aren't too 
many other M-keystrokes I use inside emacs on my tablet, anyway.

(M-arrow never seems to work for me, I'm not sure why.  Maybe that's a separate 
bug, or maybe I should just blame screen.)

Irssi is a far more common use case for me -- I Alt+N back and forth between 
channels all the time on the tablet.

Original comment by des.siam...@gmail.com on 12 Jul 2011 at 12:56

[GoogleCodeExporter]

I'll take a look - this may be a side effect of non-multitouch vs multitouch 
key handling. Which device are you using?

Original comment by Klaus.We...@gmail.com on 12 Jul 2011 at 9:04

• Changed state: Accepted

[GoogleCodeExporter]

Samsung Galaxy Tab 10.1, retail version (model GT-P7510).  Running stock 
Android 3.1.

Thanks for looking into this!

Original comment by des.siam...@gmail.com on 12 Jul 2011 at 9:39

[GoogleCodeExporter]

This issue was closed by revision a9b321709569.

Original comment by klausw@google.com on 13 Jul 2011 at 12:49

• Changed state: Fixed

[GoogleCodeExporter]

Please try v1.21rc1 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list, that should fix it.

Original comment by Klaus.We...@gmail.com on 13 Jul 2011 at 1:17

[GoogleCodeExporter]

I can confirm this fixes the problem.  Thank you very much for the quick fix!

Original comment by des.siam...@gmail.com on 13 Jul 2011 at 2:08

[GoogleCodeExporter]

Bulk update - changing "Fixed" to "Verified" for old bugs.

(Background: I'm changing the "Fixed" status to be considered open, the next 
steps in the lifecycle will be the closed states "FixInTest" and "Verified". 
This lets me mark issues as "Fixed" in commit messages without hiding them from 
the issue tracker.)

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:33

[GoogleCodeExporter]

Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34

• Changed state: Verified