Dave,
Thank you for your response. I'm not using multi-line text box, so that is
not an issue.
I'm currently using this command in the OpenCard to activate the field:
send "touchStart" to fld "ExerValue" on this card in 100 milliseconds
This creates the native text input box, but doesn't bring up the keyboard.
The color of the text box changes to the color defined in the native text
box, but when you touch it a second time Android puts a orange highlight on
the text box and brings up the keyboard. So it goes from the field not
being focused to having focus.
I also added the on keyboardDeactivated handler to the card, but that didn't
resolve the issue.
I also tried put the following in the Native Text Box Create handler.
if tOsType = "android" then
send "touchStart" to me in 300 milliseconds
end if
This just resulted in the field blinking on and off and the keyboard never
coming up. I think it was creating the Native control handler over and
over. I need a way to send focus to the Native Control. I have the
following at the end of my create function.
mobileControlDo pName, "focus" -- pName is the passed name of
the control
This doesn't do anything in Android.
Any other suggestions??????
Thanks
Dan
-----Original Message-----
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Dave Kilroy via use-livecode
Sent: Thursday, January 12, 2017 12:21 PM
To: use-revolut...@lists.runrev.com
Cc: Dave Kilroy
Subject: Re: Android Keyboard Activation Issue
Hi Dan - is your native control multi-line? If so the dictionary says
mobileControlDo multi-line text input specific actions are for iOS only.
I use a 'send' command to create native controls in the openCard handler in
500ms which works in iOS and Android. When I have more than on native input
on a card I make use of: inputFocus, mobileControlTarget, inputBeginEditing
etc.
Also I've had a problem with getting the keyboard to slide out on Android
without an extra tap so I use the following in the keyboardDeactivated
message
if isAndroid() then
focus on fld "fldInput1"
focus on nothing
end if
So it just may be that if you check exactly where the focus is before the
keyboard appears that you can cut out your extra tap...
-----
"The first 90% of the task takes 90% of the time, and the last 10% takes the
other 90% of the time."
Peter M. Brigham
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Android-Keyboard-Activation-I
ssue-tp4711601p4711612.html
Sent from the Revolution - User mailing list archive at Nabble.com.
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
