Wait command

[dunbarx at aol.com]

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 <ambassador at fourthworld.com>
To: use-livecode <use-livecode at lists.runrev.com>
Sent: Sun, Mar 2, 2014 10:23 pm
Subject: 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, allowing at least once complete cycle through the OS 
and application event loops.

This allows pending messages to be handled, and allows the OS interrupts 
enough space to be usable if something needs to be exited from, and 
allows the OS to update the screen.

A lot happens with that humble line, simply and with reasonable efficiency.

-- 
  Richard Gaskin
  Fourth World Systems
  Software Design and Development for Desktop, Mobile, and Web
  ____________________________________________________________
  Ambassador at FourthWorld.com        http://www.FourthWorld.com

_______________________________________________
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