So, after a some research I'm beginning to think there's some
disconnect, either between the iPhone OS or the simulator's
implementation that leads me to believe that the keys are not
supported at all or simply not yet.
I'm going to keep at it but at this point I'm not sure what can be
done. I'll keep everyone posted so watch this space. I'll be posting
something on the website too so I can let people know of this issue.
Why would they put the arrows on the keyboard, Apple is usually very
deliberate with their designs.
Thx
Rob
Rob Alfonso, 954pc Inc.
10222 NW 47th Street
(954) 636-2359
Sunrise, FL 33351
r...@954pc.com
http://www.954pc.com
> --
> You received this message because you are subscribed to the Google
> Groups "iSSH/iX11" group.
> To post to this group, send email to is...@googlegroups.com.
> To unsubscribe from this group, send email to issh+uns...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/issh?hl=en
> .
>
I have access to Apple's Enterprise support folks, so I could submit
this as an issue, but since the "special keys" work with Mail they
might not be that helpful.
-Dave
Escape does not do anything, but this doesn't surprise me as a close-
up image of the keyboard dock shows that it does not *have* an escape
key. But it has control and arrow keys, and a tab key.
The best image of the keyboard dock I've found, the only one that let
me read all the key caps clearly, can be found by going to the Apple
store and searching for the keyboard dock, clicking on the thumbnail
for the image of the keyboard alone, and then clicking with the
magnifying lens cursor. You then get an image big enough to read, but
you have to pan it around -- except you can then open that image in
another window. I'd post the URL here, but it's handled by Akamai, so
sharing my own URL with geographically distant people would probably
be non-optimal.
I've been studying it so as to set my expectations reasonably. I am
expecting that eventually all the functions shown on that keyboard
will be fully supported, but I'm not holding out hope for keys that
are conspicuously absent from the keyboard dock, most notably the
"escape" key (I can re-adapt to control-leftbracket, I've had to on
terminals in the past) and the "fn" key.
Some other tests: command-up-arrow also jumps to the top of the
document, and command-down-arrow also jumps to the bottom, but command-
f and command-b do *not* move the cursor forwards and backwards. So
the command key is getting through as well, and is not treated
identically to the control key. The option key behaves as MacOS has
trained me to expect. For example, option-o produces a "ø" character,
option-8 produces a "•" character, option-shift-8 produces a "°"
character, and so on. Even option-n followed by an n produces a "ñ",
by first producing a hovering tilde in a strangely colored box, and
then replacing that glyph with ñ when the n key is hit the second
time.
(Also, the bright/dim keys work, the volume keys, including mute
toggle, work, and the media playback keys work. The "eject" key is
interesting; it toggles the on-screen keyboard, bringing it up or
dismissing it. The exposé and dashboard keys do not do anything at
all.)
This is exactly the frustration I'm dealing with. The UI components
themselves receive the arrow keys and other such commands without an
issue. The problem is that in the simulator, they do make their way
back as key events to my code. On the real device, they're never sent
and I have no way of telling if they were. I think the best solution
for the moment may be to create an efficient keyboard accessory as
requested in another thread. Long term, I will file a support issue
since I figure at least receiving arrow key events will be a common
interest among a lot of apps (not just terminals but games too!) and
if I can capture the meta keys as well, that's just gravy!
Dean
I just plugged in my bluetooth keyboard and fired up iSSH and also
discovered this problem. I hope by talking to Apple you can discover
the reason for the key events not appearing... Maybe its something
fairly simple because I can't imagine that Apple would restrict use of
those keys for their own applications... to what end?
Just out of curiosity, have you tried out the OS 4 preview? I was
very pleased to see that bluetooth keyboard support was prominently
displayed as a new feature for the phones! I certainly don't want to
wait that long for ctrl support, but it would be some consolation to
know that it will work in the future.
I spent far too long trying to cobble together a solution sacrificing
a normal key using tty settings (not even close) and xmodmap (xterm
only, but still a solution perhaps) but didn't get far. xev indicates
that none of the 'special' key events seem to make it through.
I am also curious what work arounds you have in mind?
Sadly this issue makes my new iPad fail with my primary usage
scenario... remote terminal.
Good luck on this one!
On Apr 4, 6:48 pm, Dean <canada...@gmail.com> wrote:
Oh, Twitterific is probably just using a standard edit field (from
Apple) that is responding to all those keys. iSSH obviously can't be
using a standard edit field. Hmmm... my memory is being jogged by
that. Let me do some research and get back to you.
Dean
> > something on the website too so I can let people know of this issue.- Hide quoted text -
>
> - Show quoted text -
Sent from my iPad
Dan
Sent from my iPhone