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

Option to ignore physical keyboard #34

Closed
GoogleCodeExporter opened this issue Apr 1, 2015 · 5 comments
Closed

Option to ignore physical keyboard #34

GoogleCodeExporter opened this issue Apr 1, 2015 · 5 comments

Comments

@GoogleCodeExporter
Copy link

I have a droid pro, and would love to use this keyboard.  However, when in 
landscape mode it doesn't even come up, probably because it detects the 
physical keyboard is open (permanently).  Can you add a setting to ignore the 
status of the physical keyboard when in landscape mode?

Original issue reported on code.google.com by jerste...@gmail.com on 14 Jun 2011 at 8:32

@GoogleCodeExporter
Copy link
Author

I added a "Force keyboard on" preference in revision 
09a22d0cd515a3a2b3e74a4d63a40a4d886ed583, off by default.

Try v1.23rc2 (or later) from 
http://code.google.com/p/hackerskeyboard/downloads/list, and please let me know 
if that works for you.

Original comment by Klaus.We...@gmail.com on 26 Sep 2011 at 10:19

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

That fixed the issue! Thanks very much, now I can use a full keyboard
(including the ever elusive tab key) on my Droid Pro!

Original comment by jerste...@gmail.com on 26 Sep 2011 at 10:35

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

Thanks for the confirmation!

FYI, once I get a chance to work on a keyboard selection refactoring, I plan to 
add a 1-row layout that has just the missing special keys, to save space. Does 
it currently work to use the hardware keyboard together with the soft keyboard 
while the soft keyboard is forced on?

Original comment by Klaus.We...@gmail.com on 26 Sep 2011 at 10:39

  • Changed state: Verified
  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

It works just fine.  If I can make a suggestion for your 1 row layout (which
would be perfect for portrait mode), maybe add a key to bring up the full
keyboard and shrink it back down? Some things like <, >, { and } are very
hard to get to on the hardware keyboard.  In fact, while typing those
special characters, I had your keyboard on capslock and used my regular just
fine, without it being affected by your keyboard's capslock.

Let me know if I can help test anything.

Original comment by jerste...@gmail.com on 26 Sep 2011 at 11:05

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

It'll be a while before I have something for testing, but please subscribe to 
issue 13 if you want to track progress on this issue, I'll add updates there 
when I have news.

Original comment by Klaus.We...@gmail.com on 26 Sep 2011 at 11:43

  • Added labels: ****
  • Removed labels: ****

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