Re: Wait command

LOVING TYPE DEBUGGER I meant LOGGING type debugger!!! On Mar 4, 2014, at 6:53 PM, Robert Sneidar wrote: > 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

Re: Wait command

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

Re: Wait command

Pete- Monday, March 3, 2014, 9:46:16 AM, you wrote: > None. Idle handlers are the devil's playground, as they say. -- -Mark Wieder ahsoftw...@gmail.com This communication may be unlawfully collected and stored by the National Security Agency (NSA) in secret. The parties to this email do no

Re: Wait command

Thanks Richard. I already have Flight Recorder but forgot to use it for this problem. I will give it a whirl and see what transpires. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin

Re: Wait command

Peter Haworth wrote: On Mon, Mar 3, 2014 at 9:21 AM, Richard Gaskin wrote: Any idle handlers? None. Idle handlers are the devil's playground, as they say. I tend to agree. In times like this I sometimes find it helpful to be able to review a log of all execution, and made the 4W Flight R

Re: Wait command

On Mon, Mar 3, 2014 at 9:21 AM, Richard Gaskin wrote: > Any idle handlers? None. Idle handlers are the devil's playground, as they say. Pete lcSQL Software Home of lcStackBrowser and SQLiteAdmin

Re: Wait command

Peter Haworth wrote: 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

Re: Wait command

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

Re: Wait command

Richard. Just so. I spoke too carelessly, forgetting, as usual, that LC has features that HC could not dream of. Craig -Original Message- From: Richard Gaskin To: use-livecode Sent: Sun, Mar 2, 2014 10:23 pm Subject: Re: Wait command dunbarx wrote: > Wait is blocking.

Re: Wait command

dunbarx wrote: > Wait is blocking. An idle handler will be locked out just like > everything else. > > But a line like "wait 0 with messages" does not seem to me to do much. It undoes your first sentence. It calls the equivalent of what we old readers of Inside Mac used to call GetNextEvent, a

Re: Wait command

"wait 0 with messages does not seem to me to do much. > Maybe retard the flow of execution a few microseconds? > > > Craig > > > > -Original Message----- > From: Robert Sneidar > To: How to use LiveCode > Sent: Sun, Mar 2, 2014 9:13 pm > Subject: Re: W

Re: Wait command

es does not seem to me to do much. Maybe retard the flow of execution a few microseconds? Craig -Original Message- From: Robert Sneidar To: How to use LiveCode Sent: Sun, Mar 2, 2014 9:13 pm Subject: Re: Wait command Only reason I can think to put a wait command in a running script

Re: Wait command

Only reason I can think to put a wait command in a running script is to give a change for an on idle handler to be triggered. If you DO have an idle handler running somewhere and IT has a problem that causes the engine to exit to top, that might be your bugaboo. Bob On Mar 2, 2014, at 5:47 PM