Keyboard not dismissed after returninfld

[SusanB]

I only just noticed that in the parts of my app where I have returninfld, after typing in the field and pressing return, the cursor jumps to the beginning of the field and doesn’t execute any commands, exit the field or dismiss the keyboard. Subsequent return strokes just clear the field without leaving it or dismissing the keyboard. This doesn't happen in the similar iOS apps or in development on Android which doesn't show a pop-up keyboard anyway. I'm currently using v. 8.1.5 RC3, but this same problem occurred using v 6.7. I'm surprised nobody ever complained about this. I'm so eager to fix it and would greatly appreciate any help!

[MaxV]

Post a bug on http://quality.livecode.com/

[jacque]

What's in the returnInField handler? And does the field have autotab set to true?

Max is right it's probably a bug, but there may be ways around it.

[sphere]

This is one of the reasons i'm using the ask command, at least for single line input fields

[FourthWorld]

Are you using a LiveCode field, or a mobile-native field?

[sphere]

mwah, errr, yes simple field

what you mean by mobile-native is this:
mobileControlCreate "input", "myFirstInputField"

[FourthWorld]

Using a LiveCode field on mobile is very ambitious, requiring a lot of work to handle the interactions, selection handles, context menu, and even with all that you won't get normal clipboard support. The issue you've found here is just one more.

Have you considered using a mobile-native field?

[sphere]

I'm diving into it right now.
I guess i was to lazy to check it out

***edit***
yesterday evening while i was walking my dogs(like every other day), i though't this over and i remembered i was busy with a similair thing about 2 years ago, but i did not like the way it was working and found also with help from this great board that using ask was easier and found it more pleasant to work with. So once pressed in the field the ask command jumps up and afterwards the inputted data is set into the field. ( i also did the screen shifting lesson back then, when the keyboard pops-up.

[SusanB]

I haven't checked back to this topic since I've been working on my iOS version. The new comments have been so helpful. This is a great workaround, and I am grateful.

[jacque]

Asking is definitely easier but it isn't a mobile interface, in case that matters. LC's implementation is also kind of ugly.

[SusanB]

Oh boy, well the story will continue.....

[jacque]

Well, LC 9 dp 8 has a new Android field which should take care of everything automatically. But there's a bug that prevents it from working right now. I think if you wait for dp 10 you should be able to just drag the field onto a card and hopefully it will do all the work for you. We'll see when the next release comes out.

[SusanB]

The "Answer" work around worked well on my Android v. 6 tablet. But I can't load the app on my v. 7 phone for testing. It says the file is corrupted. The old version of the app doesn't even appear in the Play Store from the v. 7 phone, but is there when accessing via a v. 6 phone. I'm building with LC 9 dp 8. I guess that would be a topic for a different post....