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

Softkeys on Archos 101 overlap keyboard #12

Closed
GoogleCodeExporter opened this issue Nov 22, 2015 · 10 comments
Closed

Softkeys on Archos 101 overlap keyboard #12

GoogleCodeExporter opened this issue Nov 22, 2015 · 10 comments

Comments

@GoogleCodeExporter
Copy link

The Archos 101 has soft keys shown on the right part of the display. The 
keyboard assumes having the full display width available, so it's partially 
covered by the softkeys.

Original issue reported on code.google.com by Klaus.We...@gmail.com on 25 May 2011 at 7:38

@GoogleCodeExporter
Copy link
Author

yes, i knew this...i was just asking if there some setting to solve this (like 
there is for height of keyboard)

Original comment by spino1...@gmail.com on 25 May 2011 at 8:09

@GoogleCodeExporter
Copy link
Author

I think I found the problem, can you please try out the release candidate and 
let me know if that works as you expect? 
http://code.google.com/p/hackerskeyboard/downloads/detail?name=HackersKeyboard-v
1012rc2.apk

Original comment by Klaus.We...@gmail.com on 26 May 2011 at 1:01

@GoogleCodeExporter
Copy link
Author

I've tested the fix on my Archos 70, which uses the same firmware as the 101. 
It appears to work correctly in landscape mode, which is where the keyboard 
previously partly covered the softkeys. So, well done. Many, many other 
keyboards, including for-pay ones don't get this right.

In portrait mode, there is a transient problem. When I first switch from 
landscape to portrait mode with the keyboard active, it leaves a white blank 
space to the right of the keyboard (where the soft buttons would be if it were 
still landscape mode). However, switching back to landscape and back to 
portrait fixes this (portrait mode then displays correctly), so this remaining 
buglet may not be worth spending time fixing.

Original comment by jfmcbra...@gmail.com on 26 May 2011 at 1:22

@GoogleCodeExporter
Copy link
Author

Great Scott: it is working! ;) are you planning to release on the market
soon?

Original comment by spino1...@gmail.com on 26 May 2011 at 10:19

@GoogleCodeExporter
Copy link
Author

Yes, I plan to release it on Market, but I need to get confirmation from users 
first that the latest release candidate (v1.12rc5) is working with no 
regressions: http://code.google.com/p/hackerskeyboard/downloads/list

I'd still like to fix the glitch where the size is initially wrong until 
re-rotated, but that can wait until a later release.

Original comment by Klaus.We...@gmail.com on 27 May 2011 at 12:52

@GoogleCodeExporter
Copy link
Author

I've tested this some more, and trying again after a reboot (to make sure 
nothing else was running), the initial size in portrait problem did not require 
a re-rotation to solve. It did flicker for a moment, sizing of the keyboard and 
position of the soft buttons changing a few times, but within a second or two, 
it had settled down correctly.

Original comment by jfmcbra...@gmail.com on 27 May 2011 at 1:29

@GoogleCodeExporter
Copy link
Author

I did not had problems with size in portrait: it works like a charm, if this
can be useful ;)

I own an Archos 70it, android version 2.2.1, FW 2.3.26...rooted installing
SDE from Archos...

Original comment by spino1...@gmail.com on 27 May 2011 at 5:21

@GoogleCodeExporter
Copy link
Author

Ok, I'll treat this as fixed, and the new version should (finally) be ready for 
a Market release today. Let me know if you find a reproducible sequence where 
it's misbehaving, and I can revisit it.

Original comment by Klaus.We...@gmail.com on 28 May 2011 at 6:20

  • 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