New issue 276 by da4e...@gmail.com: External keyboard support
http://code.google.com/p/mobileterminal/issues/detail?id=276
Paired iPod touch 4 with apple wireless keyboard.
Perhaps it also apply to the wired keyboards connected to the iPads via
apple camera connection kit.
Letter, number and some modifier keys working normaly, on-screen keyboard
did not show up (as expected).
- Arrow keys don't work
- Can't use keys combinations
All that works in native apps like Notes or Safari, and some other build
for iOs 4.3
iPod Toutch 4g
iOs 4.3.1
Mobile terminal r520
I'm currently interested in having tiny, but powerful device to try some
python development. iPod touch is just great, but i cant use most of the
iOs apps to write a code (thay store it in local databases, so i can't run
it on-the-go) and i can't use nano without arrow keys.
The plan: to use my iPad 2 (iOS 4.3.3) and Logitech/ZAGG keyboard as a
lightweight development platform. But mobileterminal (520-1 per Cydia)
appears to ignore the arrow keys. Other apps honor these keys. Any known
solution for this?
-B...
Comment #2 on issue 276 by dave.sto...@gmail.com: External keyboard support
http://code.google.com/p/mobileterminal/issues/detail?id=276
Please understand MobileTerminal was created back on iOS 1
The cydia page still says "not quite done for iOS 2.x"
The code is more or less stable and changes are quite difficult as far as I
know
However, I'll mark it as accepted for now
Seconding this suggestion. I use a zaggmate keyboard. Using a text editor
(like nano) in terminal mode is not workable due to the lack of support for
arrow keys and the control key. As noted above, these keys do work
elsewhere on the iPad.
I would also like to see the Esc, Control, and Arrow Keys supported on
external keyboards. This would make vim (and most other curses supported
applications) usable and turn the iPad into a truly useful tool.
iPad2, iOS 5.0.1, Apple Wireless Keyboard, MobileTerminal r520_1
Thanks
Matt
Looks like the rejection of multi-character input in this snippet from
Keyboard.m is the culprit. Would just commenting this out fix the issue?
- (void)insertText:(id)character
{
if ([character length] != 1)
[NSException raise:@"Unsupported" format:@"Unhandled multi-char
insert!"];
[shellKeyboard handleKeyPress:[character characterAtIndex:0]];
}