Windows exe not dropping from task manager list of processes

[Jim Ault]

Thanks for the suggestions, but no luck.
Here is what is in the stack script, only one card, two buttons.
disappears < Launch only, close button >
persists < run script without a 'send', close button >
persists < run script with 'send', close button  >

on openstack
  set the destroystack of this stack to true
    set the destroywindow of this stack to true
end openstack

on closeCard -- brute-force method (from docs)
  repeat until the pendingMessages is empty
    cancel item 1 of line 1 of the pendingMessages
  end repeat
end closeCard

What else should I study in the docs?
Jim Ault

> Cancel the pending messages on quit and you should see it go away.
> 
> --
>   Richard Gaskin
>   Managing Editor, revJournal


On 9/20/05 1:26 PM, "Richard Gaskin" <ambassador at fourthworld.com> wrote:

> Jim Ault wrote:
>> This has probably been answered, but I could not find it in the archive.
>> 
>> I am compiling a tiny app that basically just gets a file from an ftp site
>> every 20-30 seconds.
>> 
>> If I launch the file, then close it, its process quickly disappears.
>> If I launch and run a script, it takes over 60 seconds to disappear.
>> If I launch and run a script that uses "send m in 10000 millisecs", then
>> close with the red-X button, it remains on the list.  Subsequent launches
>> create new processes.
>> I have set the "purge stack, window, destroystack, destroywindow" items and
>> no success.
>> 
>> What is the trick (I am a Mac guy) to avoid a client having problems with
>> exe's that don't die?