On 7/14/16, 12:26 PM, "use-livecode on behalf of Richard Gaskin" <use-livecode-boun...@lists.runrev.com on behalf of ambassa...@fourthworld.com> wrote:
>Scott Rossi wrote: > > > Thanks for checking Richard. How did you do your test? > >I had the target field trap returnInField and display its text in a >second field. Worth a try, but the second field remains empty. > > > > Using a Nexus 5X here, so recent hardware. I place a standard > > LiveCode field a card (nothing native), and in the card script: > > > > on returnInField > > answer millisecs() > > end returnInField > > > > When I press characters on the mobile keyboard, they appear in the > > field, but when I press return, the cursor moves in the field but > > nothing else happens. > >Did you include the Answer Dialog in the build? Not sure about your setup, but here, both Ask and Answer are default inclusions in Standalone Settings. Just for fun I enabled the manual "Select inclusions..." but the lack of result was the same. > > > To answer your question, focus has always been an issue for me on > > Android. > > I need to track characters and jump between multiple fields of a long > > registration key, which works as expected on iOS but unfortunately > > not on Android. The use of standard LC fields is a workaround. > >You may want to go back to Plan A with a mobile-native field. With an >LC field we have no copy-and-paste, and the text selection behaviors are >just so non-mobile that it's likely to frighten and confuse users. Well, native fields have been finicky for me on Android (and still are). Apparently unless native fields exceed a certain height dimension, they briefly show scrollbars when focused, even single line fields. Focus (perhaps only in my case) has been unreliable, and with the reg code I need to manage, the inability to auto-jump between fields is more likely to confuse users than the lack of cut and paste, so I'm not really concerned there. > >I've had pretty good luck with focus in my Android builds, across a >fairly wide range of devices (it's become a running gag in my house >every time I come home with another cheap tablet to test on). > >What issues were you having with that? The issues are what I described above. I may have gone about it ineffectively but I need to manage the entry of a reg code across 4 fields, such that: - After 4 characters are entered one a field, focus automatically jumps to the next field without the user having to do anything, and without the keyboard auto-removing itself - Text characters are automatically converted to caps - Pressing return triggers submission As I mentioned, all is working fine on iOS, so I'd like to think it's possible either with standard or native fields. Regards, Scott Rossi Creative Director Tactile Media, UX/UI Design > >-- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.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
