The easiest thing to do is to use a mobile input field, but if you aren't interested in doing that, Let's see: Crazy idea that I haven't tried 1: You might be able to trap the field getting the focus, and if it does get the focus, lock the screen until you can process textChanged, keyDown, etc., remembering to re-lock the screen each time. Crazy idea that I haven't tried 2: You might also be able to use two layers - a transparent field with transparent text and a display field with normal text. When the user does something on the transparent field, you process it and update the display field underneath. That would allow you to capture the return and ignore it.
On Wed, Sep 20, 2017 at 6:28 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > yes it does. > > Bob S > > > > On Sep 20, 2017, at 14:44 , Mike Bonner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > If "textchanged" triggers on paste, you can probably use that.. > > > _______________________________________________ > 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 > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." _______________________________________________ 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
