Hi Roger (and Jaque)
J. Landman Gay wrote > Addendum: I wasn't accounting for mobile. Both my first or second method > will likely pop up the keyboard briefly which would not be good. I think > you'll have to use the third method, which will eliminate the engine's > attempt to focus on any field. Sorry I should have been less gnomic in my earlier posting... I've encountered unwanted keyboards springing up with mobile before, and did exactly what Jacque described (but found that I had to give the engine up to a second before setting traversalOn to true to reliably avoid the keyboard appearing) ----- "Some are born coders, some achieve coding, and some have coding thrust upon them." - William Shakespeare & Hugh Senior -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Go-to-card-with-effects-is-slow-on-Android-tp4675089p4675138.html Sent from the Revolution - User mailing list archive at Nabble.com. _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
