You might want to do something to sniff out invisible conditions that your events have unwittingly created:
>From the docs: ----------------------------- Use the waitDepth function to determine how many wait commands are currently awaiting completion. Value: The waitDepth function returns a positive integer. Comments: The wait with messages form of the wait command , when used in a handler, pauses that handler while allowing Revolution to execute other handlers while waiting. The waitDepth function indicates how many such statements are currently executing--that is, how many handlers are currently paused by a wait with messages statement. If there are no paused handlers, the waitDepth function returns 1. ------------------------------ Maybe the answer lies in the 'stacking' of handlers. Jim Ault Las Vegas On 7/9/07 1:41 PM, "Dave" <[EMAIL PROTECTED]> wrote: > Hi All, > > I have a handler that gets called on a regular basis via the "send > xxx in N seconds" command. > > The handler then does some processing, but but wait for a task to > complete, to do the wait I use: > > if TaskNotDone = true then > wait 1 second with messages > end if > > I thought that this would allow other objects in the stack to > function, but this is not the case. > > How can I make it so that I can wait for the task to complete but > allow the rest of the GUI to work? > > Thanks a lot > All the Best > Dave > > _______________________________________________ > use-revolution mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-revolution _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
