The Most Stupid Question Ever?

[Bob Sneidar]

The message box is not a container. It’s a stack. A stack that tracks global properties, global variables, pending messages and stacks in use actively. It stands to reason then that it has to be either in the message path somehow. I’m not sure how that affects things, but I have noticed while attempting to track the contents of variables while a script was executing buy putting values in the msg that it doesn’t update until idle irregardless of whether I issue a wait or no, unless I use with messages.

Bob S


On Nov 11, 2020, at 3:04 AM, David V Glasgow via use-livecode <use-livecode at lists.runrev.com<mailto:use-livecode at lists.runrev.com>> wrote:

So then LC knows when the message box is about to be the target, and
therefore acts differently than with any other container. The actual already
executed  command "put" is left stranded, unrequited, because the next line
in sequence, not yet executed,  has foreknowledge that the upcoming target
is the message box, and is girding itself to access it??