New stuff available for creating/editing virtual keyboards on the N900 now available - Page 11 - maemo.org

nicolai | # 101 | 2012-09-11, 15:23 | Report

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.

The Following 4 Users Say Thank You to nicolai For This Useful Post:
freemangordon, fw190, kent_autistic, melisa queen

freemangordon | # 102 | 2012-09-12, 06:49 | Report

Originally Posted by nicolai View Post

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.

Would you attach .vkb you use to trigger the bug, so I can organize a little debugging session here

The Following 2 Users Say Thank You to freemangordon For This Useful Post:
Estel, fw190

nicolai | # 103 | 2012-09-12, 07:26 | Report

en_US.vkb layout with slide keys.

nicolai

Attached Files

en_US.vkb.gz (681 Bytes, 87 views)

Last edited by nicolai; 2012-09-12 at 07:29.

The Following 8 Users Say Thank You to nicolai For This Useful Post:
ersanpermana, Estel, freemangordon, fw190, kent_autistic, melisa queen, neboja, visN900

freemangordon | # 104 | 2012-09-18, 20:09 | Report

Originally Posted by nicolai View Post

en_US.vkb layout with slide keys.

nicolai

Should be ok now

https://gitorious.org/community-ssu/...4afefabd92dd55

The Following 7 Users Say Thank You to freemangordon For This Useful Post:
Estel, fw190, kent_autistic, mr_pingu, nicolai, OVK, sixwheeledbeast

artpra | # 105 | 2012-10-02, 07:25 | Report

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.

The Following 6 Users Say Thank You to artpra For This Useful Post:
freemangordon, kent_autistic, laith.m.y, mr_pingu, nicolai, visN900

freemangordon | # 106 | 2012-10-18, 12:06 | Report

@nicolai - as it seems you don't have time/will to continue your work on portrait VKB, would you mind to share your patches, so one to be able to continue?

The Following 3 Users Say Thank You to freemangordon For This Useful Post:
Estel, kent_autistic, visN900

nicolai | # 107 | 2012-10-18, 12:29 | Report

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 View Post

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.

The Following 6 Users Say Thank You to nicolai For This Useful Post:
Estel, freemangordon, fw190, kent_autistic, mr_pingu, visN900

freemangordon | # 108 | 2012-10-18, 12:56 | Report

Originally Posted by nicolai View Post

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:

Well, I am not sure if I got it right, please elaborate: you are waiting for a mockup to implement and that is why there is no progress? As I am a bit confused now

The Following 2 Users Say Thank You to freemangordon For This Useful Post:
Estel, mr_pingu

artpra | # 109 | 2012-10-18, 13:08 | Report

Originally Posted by nicolai View Post

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)

We should focus on 4 rows variant (5 total), to have as wide buttons as possible.

The Following 4 Users Say Thank You to artpra For This Useful Post:
freemangordon, kent_autistic, neboja, panjgoori

reinob | # 110 | 2012-10-18, 13:12 | Report

Originally Posted by artpra View Post

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.

I could swear I've seen this also in standard landscape VKB. It's one of the many reasons why I only use the physical keyboard.

The Following 4 Users Say Thank You to reinob For This Useful Post:
Estel, foobar, freemangordon, misiak