Open GoogleCodeExporter opened 9 years ago
Tests like:
+ if (keyCode == KeyEvent.KEYCODE_UNKNOWN && key == 0 && scanCode == 1)
+ key = 0x1B; // Esc
don't seem too robust. For example, with my external USB keyboard, Esc gives
KeyEvent.KEYCODE_BACK. However, scan is the same - 1, and this appears to be
pretty standard scancode (Linux kernel knows it the same way).
So, proper way to handle scancodes appears to be let existing ConnectBot key
processing to try to do its job, and the very end, instead of reporting key as
unprocessed, to check scancodes (and only scancodes) and process them. At least
that's how I do it in my fork,
https://sourceforge.net/p/chdistro-droid/connectbot/
Original comment by pmis...@gmail.com
on 4 Sep 2011 at 9:18
Have you tried the tablet branch version of connectbot yet? it works perfectly
for me on my qwerty bluetooth keyboard.
Original comment by pfngu...@gmail.com
on 11 Sep 2011 at 11:46
[deleted comment]
Just dupping report regarding tablet branch from #369:
Comment 40 by pmis...@gmail.com, Sep 12, 2011
Notion Ink Adam, Android 2.2 (BeastRom), tablet branch crashes on start.
Original comment by pmis...@gmail.com
on 1 Oct 2011 at 7:51
Original issue reported on code.google.com by
svenola....@googlemail.com
on 14 Feb 2011 at 12:36Attachments: