isawred2 / hackerskeyboard

Automatically exported from code.google.com/p/hackerskeyboard
1 stars 0 forks source link

4-rows option in landscape mode still shows 5 #175

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.Set landscape mode to 4-rows
2.go to an input field
3.

What is the expected behavior? What do you see instead?

5 rows are displayed (numbers are on their own row) instead of just 4.  
Portrait mode correctly shows only 4.

What version of Hacker's Keyboard are you using? (See top of the app's
Settings menu.) On what phone or tablet?

1.29.1288 on Motorola Xoom running ICS 4.0.3.

If applicable, does this affect the 4-row or 5-row layout, or both? Which
language(s)?

Please provide any additional information below.

Original issue reported on code.google.com by eric.sau...@gmail.com on 21 Jan 2012 at 8:08

GoogleCodeExporter commented 9 years ago
Oops, cut&paste coding error, both prefs were applied to portrait mode.

Please try v1.30rc2 or later from 
http://code.google.com/p/hackerskeyboard/downloads/list and let me know if that 
fixes the issue,

Original comment by Klaus.We...@gmail.com on 21 Jan 2012 at 8:52

GoogleCodeExporter commented 9 years ago
Test version resolved the issue.  Thanks :)

Original comment by eric.sau...@gmail.com on 21 Jan 2012 at 5:19

GoogleCodeExporter commented 9 years ago
Issue 180 has been merged into this issue.

Original comment by Klaus.We...@gmail.com on 6 Feb 2012 at 2:23

GoogleCodeExporter commented 9 years ago
[bulk bug update]

The changes from the 1.30rcX prerelease series are included in version 1.31 as 
published on Android Market, and this bug should be fixed. If it's still not 
working for you, please reopen or file a new bug. Thanks to everyone who helped 
with finding bugs and testing!

Original comment by Klaus.We...@gmail.com on 24 Feb 2012 at 6:23

GoogleCodeExporter commented 9 years ago
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 commented 9 years ago
Bulk update - changing "Fixed" to "Verified" for old bugs.

Original comment by Klaus.We...@gmail.com on 22 Jan 2013 at 7:34