Smart Keyboard Forum

Environment : Samsung Galaxy S Korean version (SHW-M110S, build umber FROYO.SL28)
Keyboard version : Smart Keyboard Pro 3.11.0-bis

How to reproduce:
1) Use the Korean 단모음 keyboard(the alternative layout), disable commas and periods, disable all dictionaries
2) Set the height of the keyboard to cover approximately 1/3 of the screen (about 250 pixes, I guess)
3) On portrait layout, push the 'ㅎ' key, and although the popup of the key appears, the input gets ignored sometimes. Other keys seem to be fine.

When the 'ㅎ' key gets ignored, LogCat shows the following error (which seems relavant to this bug):
01-13 21:14:54.254: WARN/System.err(13727): java.lang.ArrayIndexOutOfBoundsException
01-13 21:14:54.258: WARN/System.err(13727): at java.lang.System.arraycopy(Native Method)
01-13 21:14:54.258: WARN/System.err(13727): at net.cdeguet.smartkeyboardpro.KeyboardView.getKeyIndices(KeyboardView.java:1133)
01-13 21:14:54.258: WARN/System.err(13727): at net.cdeguet.smartkeyboardpro.KeyboardView.detectAndSendKey(KeyboardView.java:1181)
01-13 21:14:54.258: WARN/System.err(13727): at net.cdeguet.smartkeyboardpro.KeyboardView.onBaseTouchEvent(KeyboardView.java:1766)
01-13 21:14:54.258: WARN/System.err(13727): at net.cdeguet.smartkeyboardpro.KeyboardView.onTouchEvent(KeyboardView.java:1616)
01-13 21:14:54.258: WARN/System.err(13727): at android.view.View.dispatchTouchEvent(View.java:3844)
01-13 21:14:54.258: WARN/System.err(13727): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:936)
01-13 21:14:54.258: WARN/System.err(13727): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:936)
01-13 21:14:54.258: WARN/System.err(13727): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:936)
01-13 21:14:54.258: WARN/System.err(13727): at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:936)
01-13 21:14:54.258: WARN/System.err(13727): at com.android.internal.policy.impl.PhoneWindow$DecorView.superDispatchTouchEvent(PhoneWindow.java:1745)
01-13 21:14:54.258: WARN/System.err(13727): at com.android.internal.policy.impl.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1137)
01-13 21:14:54.258: WARN/System.err(13727): at android.app.Dialog.dispatchTouchEvent(Dialog.java:642)
01-13 21:14:54.258: WARN/System.err(13727): at com.android.internal.policy.impl.PhoneWindow$DecorView.dispatchTouchEvent(PhoneWindow.java:1729)
01-13 21:14:54.258: WARN/System.err(13727): at android.view.ViewRoot.handleMessage(ViewRoot.java:1810)
01-13 21:14:54.258: WARN/System.err(13727): at android.os.Handler.dispatchMessage(Handler.java:99)
01-13 21:14:54.258: WARN/System.err(13727): at android.os.Looper.loop(Looper.java:123)
01-13 21:14:54.258: WARN/System.err(13727): at android.app.ActivityThread.main(ActivityThread.java:4632)
01-13 21:14:54.258: WARN/System.err(13727): at java.lang.reflect.Method.invokeNative(Native Method)
01-13 21:14:54.258: WARN/System.err(13727): at java.lang.reflect.Method.invoke(Method.java:521)
01-13 21:14:54.258: WARN/System.err(13727): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
01-13 21:14:54.258: WARN/System.err(13727): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
01-13 21:14:54.261: WARN/System.err(13727): at dalvik.system.NativeStart.main(Native Method)

Some more experimets showed that it has something to do with the keyboard height : if the height goes somewhere around 1/2 of the screen, the bug rarely happens. If it goes under 1/4 of the screen, the bug almost never happens.