Re: Bug from 2014 - still causing problems

2019-10-25 Thread Iphonelagi via use-livecode
hi Jacque Yes, In the end Todd bit the bullet and did it with the native field on both iOS and Android ... now for the testing and inevitable quirks. this lesson gave initial food for thought http://lessons.livecode.com/m/4069/l/29112-how-do-i-use-native-text-controls-on-mobile But a newbie

Re: Bug from 2014 - still causing problems

2019-10-25 Thread J. Landman Gay via use-livecode
On 10/25/19 11:44 AM, Lagi Pittas via use-livecode wrote: Jacque, you do a lot of Android programming if memory serves - do you use native all the time for text input or are we just "holding it wrong"? I use native fields almost all the time. If you write a generic handler that calls mobileCon

Re: Bug from 2014 - still causing problems

2019-10-25 Thread Jjs via use-livecode
Not always. Sometimes you don't want that. But you can't turn it off. Brian Milby via use-livecode schreef op 25 oktober 2019 19:05:06 CEST: >Probably a big advantage to using native fields on mobile is >cut/copy/paste. > >Thanks, >Brian >On Oct 25, 2019, 12:46 PM -0400, Lagi Pittas via use-live

Re: Bug from 2014 - still causing problems

2019-10-25 Thread Brian Milby via use-livecode
Probably a big advantage to using native fields on mobile is cut/copy/paste. Thanks, Brian On Oct 25, 2019, 12:46 PM -0400, Lagi Pittas via use-livecode , wrote: > We are working on an App that runs on IOS/Android and Windows so making > sure > the Codebase and elements/objects are as much the sa