I vaguely remember long time, many moons, this came up. The upshot of the conversation is that because the message box is a stack file in it’s own right, certain features would only work this way, or it would interfere with other things if it didn’t work this way. I dunno, it was all all so hazy back then, what with having to watch for dinosaurs and large predators with teeth like swords.
Bob S > On Nov 10, 2020, at 12:03 PM, Bob Sneidar via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Ah! That would have to mean that script interaction with the message box is > using send in time! > > Bob S > > > On Nov 10, 2020, at 10:58 AM, Craig newman via use-livecode > <use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote: > > Not stupid. Wierder than you think. > > Substitute "field 1" for the message box. Works just fine, like it ought to. > > Craig > > -----Original Message----- > From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf > Of Bob Sneidar via use-livecode > Sent: Monday, November 09, 2020 12:04 PM > To: How to use LiveCode > <use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> > Cc: Bob Sneidar > <bobsnei...@iotecdigital.com<mailto:bobsnei...@iotecdigital.com>> > Subject: Re: The Most Stupid Question Ever? > > I have seen this sort of thing before with the wait command. Very > frustrating. Apparently Livecode is not *strictly* single threaded. > > Bob S > > _______________________________________________ > 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
