Not just Standalone problems

MisterX b.xavier at
Mon Jan 17 12:51:47 EST 2005

Thanks Richard

That was the snippet I needed! This one is for the faq 'coz after testing a
couple times, your runrev app may become like a hidden spyware or virus - PC
user habit to check ;) But im pretty sure there no more of those since there
isn't any animation showing or the game wasn't launched when I compiled the
stack... Hum...

Strange, never get eager to release I tell myself ;))

I'll remember to put a check of the pendingMessages
before sending the next animation sequence...

So pendingmessages are not a form of threading?


> -----Original Message-----
> From: use-revolution-bounces at 
> [mailto:use-revolution-bounces at] On Behalf Of 
> Richard Gaskin
> Sent: Monday, January 17, 2005 17:43
> To: How to use Revolution
> Subject: Re: Not just Standalone problems
> MisterX wrote:
> > I'll try it. As Richard said, I imagined it would quit when 
> the last 
> > window was closed.
> What I wrote was this quote from the docs:
>      A Revolution application quits automatically when all
>      its windows are closed and all waiting messages have
>      been handled (including messages sent with the send
> time form of the send command).
> With HyperCard, SuperCard, OMO, etc., when the last window's 
> gone it's 
> over.   The important point in that snippet is the introduction of 
> timers to the equation, something most other xTalks don't 
> have and which are commonly used in game development, so it 
> seemed worth posting.
> You can cancel all pending messages like this:
> on KillAllPendingMessages
>     repeat for each line i in the pendingMessages
>       cancel (item 1 of i)
>     end repeat
> end KillAllPendingMessages
> --
>   Richard Gaskin
>   Fourth World Media Corporation
>   __________________________________________________
>   Rev tools and more: 
> _______________________________________________
> use-revolution mailing list
> use-revolution at

More information about the Use-livecode mailing list