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
Hmm - Dan both Andrew and I appear to create native inputs on opening the card so that when the user touches the native control it's ready to go. You appear to create the native control at the same time the user touches the underneath field? (or maybe you have a round-rect graphic or similar that 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
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

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
Here is a card script I'm currently using that seems to work in an iOS/Android app I have now: on preOpenCard inputCreateTsm end preOpenCard on inputCreateTSM put the rect of graphic "tsmRectangle" into tThisRect # do some math to visually accommodate a roundedRect with innerShadow