Add optional "hide keyboard" key or option?
Brought to you by:
starssoft
Originally created by: Klaus.We...@gmail.com
Originally owned by: Klaus.We...@gmail.com
Some devices such as the Kindle Fire apparently don't have the usual "Back" button behavior to close the keyboard, they instead have an explicit button on the keyboard to do so.
Consider adding a similar option for this keyboard - this should of course be optional to avoid using up space for people who don't need this feature. Maybe defer until customizable maps (issue 13) are ready?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
I've added support for configurable keyboard swipe gestures, by default "swipe down" closes the keyboard.
Try v1.28rc13 or later from http://code.google.com/p/hackerskeyboard/downloads/list, and please let me know if this works for you.
Status: FixInTest
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Issue 54 has been merged into this issue.
Related
Tickets:
#54View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: sixofsp...@gmail.com
I also have the Kindle Fire, thank you for adding the swipe-down to close keyboard function. Unfortunately it does not work 100% of times: I use Dolphin browser - it works for some websites eg. google search but not others eg. this website "Search" box.
Is it possible you make the "close keyboard" action into a button like the Kindle Fire keyboard, or make this action available with a combination of keys eg. <Esc> <down> buttons?
Many thanks.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
The swipe down action is currently a bit finicky to trigger, I haven't looked into adjusting the sensitivity thresholds yet. Are you sure it's really dependent on the application or web page, or is it just having problems recognizing the gesture consistently?
In recent prereleases you can also bind actions to the Volume Up/Down hardware buttons which tends to work much more reliably. These bindings are only in effect while the keyboard is visible, so it shouldn't interfere too much with normal use of the volume keys.
Adding a specialized "close keyboard" key to the onscreen keyboard will have to wait for customizable keymap support (issue 13) - it's something most users don't need, and in the current system it would be very messy to add the key conditionally. Patience please.
As another alternative, there's already support for a persistent notification that can be triggered to open the keyboard. If the notification works on the Kindle Fire, it would be easy to change it into a toggle that closes the keyboard if it's already open.
Related
Tickets: #13
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: m...@utterlymundane.org
That (the notification toggle) would work in a lot of cases. Unfortunately,
my main use case is when using ConnectBot fullscreen, which also hides the
status bar. Having the keyboard displayed here stops the normal tap-to-show
for status bar and soft home/menu.
The swipe to hide IS working well for me, though, on the Fire (I haven't
tried on other devices), in ConnectBot. As nice as a hide button would be,
I now consider the keyboard totally usable for me. Thank you!
Mark.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
[Bulk bug update] The new Market release 1.29 includes the changes from the v1.28 prerelease series, and these "FixInTest" issues should now be fixed. If not, please reopen the bug with additional information. If the original bug covered multiple separate issues that aren't all addressed, please open new bug(s) for the leftover ones.
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
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.)
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Klaus.We...@gmail.com
Bulk update - changing "Fixed" to "Verified" for old bugs.
Status: Verified