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 the user clicks on?).
Do you get the same need for a double-touch if a user comes back to a native control a second time (i.e. when it has already been created)? Perhaps experiment with creating the native control first and then use it once it's been fully instantiated? BTW my wording earlier when I was talking about having an issue on Android with "the keyboard sliding out" was sloppy - I was trying to say the issue was around getting the keyboard to slide out of the way i.e. at the end of the editing process... Good luck! Dave PS: do you have any LiveCode fields on the card with traversalOn set to true that may be 'holding on' to focus and thus requiring the double-touch? ----- "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-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 to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
