Standalone still active in Windows Task Manager (XP) after Quitting

PaulBuzzy at aol.com PaulBuzzy at aol.com
Tue Aug 17 09:45:25 EDT 2004


I am writing a fairly complicated standalone application called ScrapDiary 
using Runtime Revolution. ScrapDiary is a calendar-based app. that can store 
pictures, movies, sounds, and text on each page. The main stack has several 
substacks for handling sound recording, video input, a floating calendar etc. I 
store the information in a separate stack which is created at runtime. When 
ScrapDiary first opens, I have a startup script that opens the splash screen window 
(modal - closes after a set time or when the user clicks on it). I also have 
a preopen stack script in the main stack that opens and closes a hidden 
calendar substack (a crude way of setting up some variables in the substack). I have 
about eight substacks, some of which use some global variables setup in the 
main stack.
Now, I have run into a major problem when I create the standalone. When I 
open and close ScrapDiary, “ScrapDiary.exe” shows up in the list of processes in 
the Windows Task Manager running under Windows XP. The standalone uses some 
of the externals (revspeech.dll and revvideograbber.dll). Now here is the 
strange thing. If I prevent two of the substacks from opening during startup and 
preopen stack (the splash screen and calendar substack), I don’t get the problem.
Now, if I create a very simple stack with no substacks and include a button 
that references the revSpeak command on mouseUp, everything is fine if I simply 
open and close the stack. If I click the button and use the revSpeak command, 
the standalone also remains in the process list of Windows Task Manager, even 
after quitting.
I am not sure if the reference to the externals (revSpeech etc.) are the 
reason for the problem in ScrapDiary, but they seem to be in the simple stack. I 
have played around with the destroyStack and destroyWindow settings to no avail.
Please let me know what I may be doing wrong. Thank you.


More information about the use-livecode mailing list