RE: Android Keyboard Activation Issue

2017-01-13 Thread Livecode XAC via use-livecode
m: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Richard Gaskin via use-livecode Sent: Friday, January 13, 2017 1:16 PM To: use-livecode@lists.runrev.com Cc: Richard Gaskin Subject: Re: Android Keyboard Activation Issue Livecode XAC wrote: > Right now I'm creati

Re: Android Keyboard Activation Issue

2017-01-13 Thread Richard Gaskin via use-livecode
Livecode XAC wrote: > Right now I'm creating the control when the user touches on the > text box and then delete the control when they enter the return. > This provides a highlight of the field that is being entered, > but has the double click issue. Regardless how the field is created, it seems

RE: Android Keyboard Activation Issue

2017-01-13 Thread Livecode XAC via use-livecode
ecode-boun...@lists.runrev.com] On Behalf Of Dave Kilroy via use-livecode Sent: Friday, January 13, 2017 5:48 AM To: use-revolut...@lists.runrev.com Cc: Dave Kilroy Subject: RE: Android Keyboard Activation Issue Hmm - Dan both Andrew and I appear to create native inputs on opening the card so that when the user t

Re: Android Keyboard Activation Issue

2017-01-13 Thread Richard Gaskin via use-livecode
Livecode XAC wrote: > mobileControlDo pName, "focus" -- pName is the passed > name of the control > > This doesn't do anything in Android. Either that's a bug or there must be some other reliable means of focusing a mobile-native field. -- Richard Gaskin Fourth World Systems So

RE: Android Keyboard Activation Issue

2017-01-13 Thread Dave Kilroy via use-livecode
/runtime-revolution.278305.n4.nabble.com/Android-Keyboard-Activation-Issue-tp4711601p4711631.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 t

RE: Android Keyboard Activation Issue

2017-01-12 Thread Andrew Bell via use-livecode
le", "line" mobileControlSet pName, "manageReturnKey", false mobileControlSet pName, "keyboardStyle", "default" mobileControlSet pName, "clearButtonMode", "unless editing" end if -- Focus on the Control mobileContr

RE: Android Keyboard Activation Issue

2017-01-12 Thread Livecode XAC via use-livecode
nuary 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' comm

Re: Android Keyboard Activation Issue

2017-01-12 Thread Dave Kilroy via use-livecode
me." Peter M. Brigham -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Android-Keyboard-Activation-Issue-tp4711601p4711612.html Sent from the Revolution - User mailing list archive at Nabble.com. ___ use

RE: Android Keyboard Activation Issue

2017-01-12 Thread Livecode XAC via use-livecode
, "default" mobileControlSet pName, "clearButtonMode", "unless editing" end if -- Focus on the Control mobileControlDo pName, "focus" -- actually focus on the field so the keyboard pops up end inputCreatorWide Mine is mo

Re: Android Keyboard Activation Issue

2017-01-12 Thread Andrew Bell via use-livecode
nput", "textAlign", "center" mobileControlSet "TSMinput", "visible", true # make sure the field has focus, which activates the keyboard mobileControlDo "TSMinput", "focus" end inputCreateTSM on closeCard # delete the

Android Keyboard Activation Issue

2017-01-11 Thread Daniel Pierce via use-livecode
List, I have developed a cross platform mobile app for iOS and Android using LiveCode and it is working OK, but I continue to get a common complaint from Android users that when they select a field the keyboard does not activate like on other apps. This is not an issue on iOS because a when