LiveCode Forums.

Hi LiveCoders

I'm experiencing an issue with the Android soft keyboard when the device is in landscape orientation, but only on recent versions of Android. I don't know if LiveCode is to blame, or the Andoid OS, or the Java SDK, or the Android SDK, or what.

Here's what happens:
Suppose a LiveCode app is running on Android Lollipop, and the device is in landscape orientation. There are two (LiveCode) text input fields on the card and you tap in the fist field which brings up the Android soft keyboard. So far so good. Then, with the soft keyboard still showing, you tap in the second input field and... where's the keyboard gone to? Then you tap in the first field and sure enough, the keyboard comes back. Tap again in the second field while the keyboard is showing and... keyboard gone again.

Run the same app on Android Gingerbread and there's no issue.

Can somebody help me determine whether its a LiveCode bug or not?

Hi Ledigimate,

Do you see the same behavior in other (non-LiveCode) apps running on Android Lollipop? If this is the case, then maybe the "problem" is in the Android OS. If not, then it might be LiveCode's fault.

Best,
Panos
--

Hi Panos

I would like to test this, but I am a bit afraid of installing Android Studio because it might mess up my Android SDK settings which could render LiveCode unable to build an Android standalone.

Perhaps someone already has Android Studio installed and could test it for us?

Regards,

Gerrie

I think Panos just means any other app you may already have installed. I just tried it with Google Keep and another note taking app and the keyboard remains until no text field is being edited.

Since the keyboard disappears when the field loses focus, you might try locking messages after the first field gains focus. Or you may be able to trap focusOut or closefield or one of the other messages to prevent the engine from getting them. Jus a guess but worth a try.

Hi all,

Yes, I meant any other (non-LC) app you have already installed. I tested using Gmail app and I do not see this behavior, so on a first glance it looks like a bug in LC. I suggest you file a report (http://quality.livecode.com/) so we investigate this further.

Best,
Panos
--

I've submitted a bug report: http://quality.livecode.com/show_bug.cgi?id=18058