How to tell when IDE is done loading

Richard Gaskin ambassador at fourthworld.com
Sun Dec 28 11:23:46 EST 2014


Mike Bonner wrote:

> Unless there is a "wait with messages" somewhere along the line
> in that big startup handler I mentioned in the previous post,
> the send that you do should be dumped at the end of the queue
> and not fire until things are done.

I had thought so myself, but apparently it varies by OS - see the 
discussion in this request submitted by a RunRev team member for 
messages that fire on idle:
http://quality.runrev.com/show_bug.cgi?id=13585

Initially I chimed in there thinking the request was in error, that 
timers would always fire only after other handlers were completed. Peter 
Brett's notes in Comment 7 there describes the details:

     Currently, the ordering is platform-dependent.  On some platforms,
     overdue engine messages are processed before overdue system events.
     On other platforms, engine events are processed before engine
     messages if the oldest engine event is older than the most overdue
     engine message.

That comment contains other info about why idle messages aren't a good 
alternative, well worth reading for those with an interest in such 
details.

-- 
  Richard Gaskin
  Fourth World Systems
  LiveCode training and consulting: http://www.fourthworld.com
  Webzine for LiveCode developers: http://www.LiveCodeJournal.com
  Follow me on Twitter: http://twitter.com/FourthWorldSys




More information about the use-livecode mailing list