[watzone69]

Originally Posted by Reef48

Sure just do the math then add it to the total size in the skin.txt landscape file. Not sure what you are trying to add....
All examples from Wvga, but you'll get the picture:

ResolutionBegin 800 480
Size 800 222

So, this is whole screen resolution and the size of the keyboard. Make the keyboard less in height. Save the file, load it to device and try reloading. You will see that keyboard has "shifted down", but row space stayed the same.

Then move on to the land-01-eng.txt (or whatever you're using) and start reducing the numbers that control horizontal row placement.

For example:

;ROW1:
Key 4 5 56 62

That's 4 pixels from the left side, 5 pixels from the top, and key dimensions are 56x62. Basically, you will see that in that row all keys have 5 as the number that defines key position distance from the top of the keyboard.

Next row has this set to 79, and the last row has it set to 153. Basically - it's a guessing game. We usually leave 10-20 pixels of row space between the keys, but you can reduce that for VGA or any size.

To calculate what would be best numbers for horizontal key placement you start from the top. Say you wanna keep 5 pixels distance from the top, and you also want all your other rows to have 5 pixels distance between them.

5 + 62 (key height) = 67
67 + 5 + 62 (key height again) = 135

And there you have them: 5 is pixel distance from the top edge for the first row of keys, 67 for the second, and 135 for the last bottom row of keys. All of the rows have 5 pixel spacing between them.

You can also use this to calculate keyboard height:
135+67+5=207. And there you have it! 207 pixels would be the number you would enter into land-00-types.txt

So, to narrow down the keyboard row space you first have to reduce the "frame box" in which the keyboard sits, and then shift the keys up a little bit.
This may help you some. Good luck. Let me know how it turns out.

Reef, you just made my day (again).

I have been trying to figure all of that stuff myself but I was making it WAY more complicated than it really is!

Thanks (again)!!