Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ConnectBot workarounds for other ssh/VNC style applications? #36

Closed
GoogleCodeExporter opened this issue Sep 30, 2015 · 6 comments

Comments

@GoogleCodeExporter
Copy link

The keyboard has special handling as a workaround for ConnectBot's inability to 
recognize the key events for special keys, it sends escape sequences for keys 
such as PageUp/PageDown and F1-F12.

This workaround is currently only active specifically for the "org.connectbot" 
package: https://market.android.com/details?id=org.connectbot, as reported by 
the EditorInfo data: 
http://developer.android.com/reference/android/view/inputmethod/EditorInfo.html

Arguably, the correct fix would be for the ssh application to send the right 
sequences when it gets the corresponding key events such as KEYCODE_F1, since 
that would also make the application work correctly for hardware keyboard 
input. Also, sending the escape sequences isn't likely to work right for VNC / 
remote desktop style applications since those generally expect to handle true 
key events as distinct units.

Open issues:

- is there a compatible way to tell that the input view should be treated as a 
shell window? As far as I can tell this isn't possible without cooperation from 
the application, since the standard edit view types don't include a type for 
that.

- we could define an EditorInfo.privateImeOptions string that applications 
could set to request shell window handling, but that would require a change to 
the ssh application(s), and if they are getting changed anyway they should add 
code to handle the extra keys directly.

- add a method for the user to tell the keyboard that it should activate this 
workaround for specific applications? For example the Irssi version of 
ConnnectBot. This would be nice in combination with a more general app-specific 
configuration override system.

Original issue reported on code.google.com by Klaus.We...@gmail.com on 15 Jun 2011 at 8:19

@GoogleCodeExporter
Copy link
Author

Issue 35 has been merged into this issue.

Original comment by Klaus.We...@gmail.com on 15 Jun 2011 at 8:19

@GoogleCodeExporter
Copy link
Author

Is there a way to make <esc> and <ctrl> keys to work with Irssi ConnectBot?
Otherwise, most of the usual linux application can't be used.

Original comment by pierre.f...@gmail.com on 30 Jun 2011 at 1:21

@GoogleCodeExporter
Copy link
Author

Can you please try v1.21rc3 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list ? It activates the 
workarounds for the irssi and pslib connectbot variants.

Original comment by Klaus.We...@gmail.com on 18 Jul 2011 at 11:42

  • Changed state: Started

@GoogleCodeExporter
Copy link
Author

Closing, current prereleases support it.

Original comment by Klaus.We...@gmail.com on 25 Sep 2011 at 11:27

  • Changed state: Fixed

@GoogleCodeExporter
Copy link
Author

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
Copy link
Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant