For this case, though, it will have to be called up specially, not made to look like it was already there.
The field in question also allows users to put in images - something I don't think native fields can do. So the app would have an enter text button that calls up the native field, where the user can type or paste text that is then inserted into the LC field. Sent from my iPhone > On Jun 26, 2017, at 3:21 PM, Dave Kilroy via use-livecode > <use-livecode@lists.runrev.com> wrote: > > OK good, the visible bits of a native field (border, background colour etc) > could all be provided by background graphics so when you switch fields no > visible change can be seen - you might even be able to use the > inputTextChanged message instead of a button which the user has to press > > BTW you’ll have to delete the native field instead of just hiding it as it’ll > be in the top layer and could interfere with user interactions… > > Dave > > >> Hi Dave - I think that might help >> >> I could give the user a button for opening up a pastable field. They could >> paste into that and LC could process it and put it into the regular field. >> It's not a bad idea. > _______________________________________________ > 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 _______________________________________________ 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
