Originally Posted by nicolai

From this line
https://gitorious.org/community-ssu/...rer.c#line1846
it appears slide key characters are stored at key->label field
with
1. no key is pressed (line 1857)
at offset 0 and every subsequent key with 4 byte offset.
2. current_slide_key > 1 (line 1829)
at offstet 4 * (key->current_slide_key - 1) % byte_count
3. I am not quite sure what this does (line 1839)

But even if no key was pressed, at key->label[0] is no key char.
The Keyboardlayout I use has a button with a slide key with
12 keys. The first character is not at offset 0 but at offset 56
and the next characters are at offset 56 + 16*x
Whereas this "56" depends on number of slides (bytecount in
structure vkb_key). Using a slide key with 6 keys (bytecount) this offet
is 32. (offset = ((byte_count >> 1) + 1) << 3
But only after loading the vkb the first time. Changing the language,
this memory location holds only garbage.

Originally Posted by nicolai

en_US.vkb layout with slide keys.


nicolai

Originally Posted by nicolai

Need some help, please create some mockups for portrait mode
keyboard, but notice the menu/space/enter buttons on the bottom
are fixed and not defined by the keyboard layout xml. The
shift and backspace use a fixed size icon of 72x70 pixels.

Originally Posted by nicolai

You could merge hildon-input-method-plugins with
my portrait-orientation-support branch.

This only changes the spacebar width and makes
the keyboard support the portrait mode flag.

I have another patch for loading
an extra portrait-mode keyboard layout.

But this code depends on what kind of portrait-mode keybaord layout
we want to have (3 rows with slide keys or 4 rows with wider keybuttons)
Therefore I need a good keyboard layout suggestion which
matches mentioned conditions:

Originally Posted by nicolai

But this code depends on what kind of portrait-mode keybaord layout
we want to have (3 rows with slide keys or 4 rows with wider keybuttons)

Originally Posted by artpra

There is one BIG problem with stock virtual keyboard forced to portrait mode, which I forgot to mention and hope for fix: sometimes it doesn`t respect cursor position. You put cursor somewhere in the middle of your text line to add some word, on the virt. keyboard view everything is ok, but in edited text field it is messed.
It happens quite often.