Custom Keyboard Problem

How are you defining these "Buttons" ?

HI @Martin KJELDSEN​ 

The Layout is defined as follows:

static const Keyboard::Layout layout =
{
 BITMAP_NUMERICKEYBOARD_ID,
 keyArray,
 10,
 callbackAreas,
 2,
 Rect(0, 0, 272-7, 88),
 TypedText(GetText(T_KEYBOARD_NUMERIC_TEXT_ENTERED, Typography::F_30_PT)),
 0xFFFF,
 Typography::F_30_PT,
 0xFFFF
};

And the Keys:

static const Keyboard::Key keyArray[10] =
{
 { 1, Rect(0 + 88 * 0, 88 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 { 2, Rect(0 + 88 * 1, 88 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 { 3, Rect(0 + 88 * 2, 88 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 
 { 4, Rect(0 + 88 * 0, 153 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 { 5, Rect(0 + 88 * 1, 153 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 { 6, Rect(0 + 88 * 2, 153 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 
 { 7, Rect(0 + 88 * 0, 218 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 { 8, Rect(0 + 88 * 1, 218 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 { 9, Rect(0 + 88 * 2, 218 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID},
 
 {10, Rect(0 + 88 * 1, 283 * 1, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID}
};

And the KeyMapping:

static const Keyboard::KeyMapping KeyMappingsNum[10] =
{
 { 1, 49}, // 1
 { 2, 50}, // 2
 { 3, 51}, // 3
 { 4, 52}, // 4
 { 5, 53}, // 5
 { 6, 54}, // 6
 { 7, 55}, // 7
 { 8, 56}, // 8
 { 9, 57}, // 9
 {10, 48} // 0
};

Hope this helps.

/jimmii

The texts are suspiciously offset by what is probably 88 pixels for each row. I think maybe it would be easier if you sent the project. Just for fun, could you try putting in absolute coordinates rather than calculating them?

/Martin

It's not that easy - it's a confidential project.

I'll try to strip it down to the minimum.

But why is the keyboard displayed correctly in the simulator?

Hey @Martin KJELDSEN​ 

OK, I will try to strip it down.

In the meantime I did some tests. I only displayed one digit to keep it simple.

With this code (Button coordinates 0/0)

static const Keyboard::Key keyArray[1] =
{
 { 1, Rect(0, 0, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID}
}

I get this (which is correct, the label is "underneath" the active button):

With coordinates (88/0):

static const Keyboard::Key keyArray[1] =
{
 { 1, Rect(88, 0, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID}
}

I get: (Button moved correctly in x-position but the label is at the wrong position)

With coordinates (0/88):

static const Keyboard::Key keyArray[1] =
{
 { 1, Rect(0, 88, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID}
}

Again, the button moved correctly in y-position, the label also moved but at the wrong position.

With coordinates (88/88):

static const Keyboard::Key keyArray[1] =
{
 { 1, Rect(88, 88, 82, 62), BITMAP_NUMERICKEYBOARDBUTTON_ID}
}

The button and the label are at the correct position (label underneath the active button)

It seems as the label corrdinates are not translated correctly. I'm using the display in portrait mode. Is there a difference as how the simulator translates the coordinates in comparison to the "target" code?

Maybe you can reproduce this with the sample keyboard code (I also took that code and adapted it to my requirements)

In the meantime I will provide the code for you.

Thanks a lot.

/jimmii

Hi @Martin KJELDSEN​ 

Any suggestions?

Could it be related to the use of the ARMCLANG library?

Regards, /jimmii

Hi jimmii,

Thanks for the update. It shouldn't have anything to do with ARMCLANG specifically. It may have something to do with the orientation,but i also kind of doubt that. I'll try to check out your project and maybe replicate this on my own end.

Thanks!

/Martin

Hey @Martin KJELDSEN​ ,

Any news / luck on this?

Thanks a lot!

/jimmii

Hello @Martin KJELDSEN​ 

Quick update:

I'm putting all RW and ZI data to external SDRAM, which works perfect for me and I didn't have any problems.

But the Keyboard causes problems with this configuration as described above.

After moving the Keybord Configuration to interal ram (RW and ZI) the Keyboard is working fine as expected.

Any idea why this is a problem? Maybe you can reproduce this behaviour at your end?

External sdram configuration and initialization is well tested and is working in other parts of the code.

/jimmii