Wait command

[Robert Sneidar]

Debug stepping through code will not show you the effects of wait 0 seconds because the step debugger itself (if I am not mistaken) is idling in between each command executed. Wait is implied here. The engine is already “waiting” in between every command executed. This BTW is one of the reasons I think Jerry Daniels came up with Remo, which had a loving type debugger and NOT a step debugger. Some things simply cannot be monitored correctly with a step debugger. 

Bob


On Mar 3, 2014, at 9:00 AM, Peter Haworth <pete at lcsql.com> wrote:

> Thanks to all for the replies, especially Geoff's clear example.  That
> explains why I could not duplicate the bug I was chasing while in debug
> mode, since clicking any of the debug icons when on the wait command
> generated the usual mouse messages.
> 
> However, I still don't understand why the "wait 0 with messages" command
> caused the rest of the statements in my script to be ignored.  There was no
> other user interaction going on at the time so there should not have been
> any messages being fired. Even if there were, shouldn't control have passed
> back to my script after the message had been processed?  I suppose a "send
> in time" command could have triggered but I don't think I have any of those
> in this application.
> 
> 
> Pete
> lcSQL Software <http://www.lcsql.com>
> Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
> SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode