MudaliarArun / connectbot

Automatically exported from code.google.com/p/connectbot
Apache License 2.0
0 stars 0 forks source link

configuration options about orientation don't match the hero (and related problems) #192

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
This is on the Hero.

What steps will reproduce the problem?
1. Turn the phone on its side
or
2. Configure the rotation settings
3. Set the rotation settings to "force landscape"

What is the expected output? What do you see instead?
1. Automatic rotation detected by the accelerometer (obeying the system
wide preferences)
2. The settings seem to be particular to a diferent model (popping out the
keyboard)
3. When I turn it now, the rotation switches to landscape, but there seems
to be no way to get the virtual keyboard.  Actually I'm having problems
with the virtual keyboard disappearing in general and not being able to get
it back unless I switch back to the menu, and then switch back to the session.

What version of the product are you using (you can see this by using Menu
-> About in the Host List)?
1.5.4

What type of system are you trying to connect to?
Debian

If you are able to connect, what is the output of "echo $TERM", "uname -a",
and any other relevant information on the host?
I can't echo $TERM since I don't have a $ on the virtual keyboard and
switching to numeric mode doesn't work (as described in issue 166) but I
know it's normally rxvt-unicode, and it's a 2.6.26 kernel.

Please provide any additional information below.
A couple of related things:
- The help section on keyboard shortcuts also seems to be particular to a
different model.
- Since using a virtual keyboard, mistakes are frequent, it would be
awesome to somehow mimic the predictive mode that we have in text messages,
email etc.
I used to have putty on a nokia phone, and the way that worked was that you
would pop up a box to write a line in, rather than directly into the shell,
and that way you could get the line completely accurate before sending it.
 Just typing directly into the shell with the virtual keyboard is a bit
tricky.  We don't seem to be able to "touch" in the line to jump the cursor
to a point to correct it either, which means having to backspace over many
characters just to fix one typo.

Original issue reported on code.google.com by penelope...@gmail.com on 1 Sep 2009 at 6:16

GoogleCodeExporter commented 8 years ago
I would encourage you to open individual tickets for each problem. Otherwise it
becomes difficult for me to know whether I've answered all your issues.

1. There seems to be something peculiar with the Hero and autorotation. It 
works fine
with the Google Ion I have. I don't have a Hero phone to investigate this 
problem.

2-3. Download the development version to add a little keyboard icon when you 
tap the
screen.

I also encourage you to read UsageWithSoftKeyboard in the Wiki section for some
caveats. Basically there are some design decisions made in Android with IMEs 
that are
beyond my control. When you bring up a virtual keyboard in landscape mode, the 
screen
won't resize to be above the keyboard (this is covered in the wiki page I 
pointed out).

The box to write in is covered by Issue 81 and you might want to click the star 
next
to that issue if you want to receive updates.

Original comment by kenny@the-b.org on 2 Sep 2009 at 11:56