search

alssade12 / hackerskeyboard

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

"Standard" keyboard rendered too small in portrait mode #8

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Open keyboard in portrait mode on phone with resolution of 800 x 480
2.
3.

What is the expected output? What do you see instead? Expected output is the 
keyboard displayed like the regular Gingerbread keyboard  Instead you see a 
compressed keyboard (screenshots from LG Optimus 2X running Android 2.2)

What version of the product are you using? On what operating system?
1.11 - tried on LG Optimus 2X on Android 2.2. Also tried on ZTE Blade running 
Android 2.3 (Cyanogenmod 7).

Please provide any additional information below.

Original issue reported on code.google.com by edremez...@gmail.com on 24 May 2011 at 3:09

Attachments:

GoogleCodeExporter commented 8 years ago 
You adjust the portrait screen percentage height in the settings menu brought 
up by the gear like key on the lower left.

However, I think that until you've gone into that menu for the first time, it 
may be artificially smaller than the setting.  Mine was *tiny* but when I went 
into the menu it said 35%.  I changed it to 50% which was huge.  Changed back 
to 35%, and much larger than it originally was.  So perhaps the setting does 
not properly initialize?

Original comment by cs07...@gmail.com on 24 May 2011 at 4:10

GoogleCodeExporter commented 8 years ago 
It's strange. It changes the height when using the full keyboard in portrait 
mode (which isn't usable on a phone), but doesn't change the height of the 
standard 4 row keyboard.

Original comment by edremez...@gmail.com on 24 May 2011 at 4:20

GoogleCodeExporter commented 8 years ago 
I think I have an idea what's going on here. As you've seen the height setting 
only applies to the full keyboard, the 4-row one uses the default scaling 
methods which is rather roundabout. 

I'll see if I can get this unified, probably the right thing to do would be to 
use 80% of the configured full keyboard height so that the rows are the same 
height. That way, the 4 rows + completions bar should be about the right size.

Original comment by Klaus.We...@gmail.com on 25 May 2011 at 5:19

GoogleCodeExporter commented 8 years ago 
I now believe my comment about the height setting not "taking" until changed 
was mistaken... I had enabled the 4 row keyboard during the same visit to the 
options menu, and it was probably that which made the percentage setting 
effective.

Original comment by cs07...@gmail.com on 25 May 2011 at 5:56

GoogleCodeExporter commented 8 years ago 
I remember that when the Gingerbread keyboard first came out, there was a 
similar issue with it. It was temporarily resolved by changing the LCD density, 
but I don't know how the proper fix was made.

Original comment by edremez...@gmail.com on 25 May 2011 at 7:56

GoogleCodeExporter commented 8 years ago 
This should be fixed in the latest release candidate (>= v1.12r5), it applies 
the height setting to the 4-row keyboards too: 
http://code.google.com/p/hackerskeyboard/downloads/list

Can you please let me know how that works for you? I can't reproduce the odd 
sizing you had reported on my phone.

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

GoogleCodeExporter commented 8 years ago 
Thanks - it works fine now! The letters could be bigger, but that's purely 
aesthetic. Please see attached screenshot (not sure why it looks trandparent, I 
think it was the scrreen capture app, as its completely opaque.

Original comment by edremez...@gmail.com on 27 May 2011 at 10:52

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks for testing! The fixed version should be on the Market later today.

The key label size is dependent on the DPI setting for the device, I think 
there isn't any easy way to fix that without breaking it for other devices or 
adding ugly workarounds.

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

GoogleCodeExporter commented 8 years ago 
Thanks - I'll download it.

Original comment by edremez...@gmail.com on 1 Jun 2011 at 10:19

GoogleCodeExporter commented 8 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 8 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