Re: Standalone app as Frankensteinian Monster

2006-10-27 Thread Mark MacKenzie
Hi Ken. Thanks, however, upon trying this, the d**n thing still won't die. I think I shall have to strip all (mainly) development functions out of the main stack/splash screen and start again with the stand alone. Let you know how things turn out with this evening's coding. So close, so

Re: Standalone app as Frankensteinian Monster

2006-10-27 Thread Ken Ray
On 10/27/06 9:08 AM, Mark MacKenzie [EMAIL PROTECTED] wrote: Hi Ken. Thanks, however, upon trying this, the d**n thing still won't die. What is your indicator that it hasn't quit? That it still shows up in the process list? Also, what platform is this on? Knowing that might help one of us

Re: Standalone app as Frankensteinian Monster..SOLVED!

2006-10-27 Thread Mark MacKenzie
Well, time to fess up. I thought I had taken care of all of the simple, obvious stuff. However, I found another handler with the exact same coding for closing my application which I had missed and which was actually trying to close the application. All my troubleshooting efforts were

Standalone app as Frankensteinian Monster

2006-10-26 Thread Mark MacKenzie
Hi. After a few month's work I am debugging the stand alone side of my application. So far the app works really well and with a complacent gleam in my mind's eye I click on the quit button of the main stack and my application won't die! The program is in two parts really. There is a Rev

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread FlexibleLearning
Hi Mark Well, it looks like you are doing a lot of unnecessary stuff. If you want to 'quit', all pendingMessages will terminate and all stacks will close automatically. If I read you right you need you only need... on closeStackRequest -- confirm whether to close the window answer question

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread Mark Schonewille
Hi Hugh, On Windows, you need to cancel pending messages, close all stack, stop externals and stop running handlers to make sure that your application really quits. Best, Mark -- Economy-x-Talk Consultancy and Software Engineering http://economy-x-talk.com http://www.salery.biz Get

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread Dar Scott
On Oct 26, 2006, at 12:47 PM, Mark Schonewille wrote: On Windows, you need to cancel pending messages, close all stack, stop externals and stop running handlers to make sure that your application really quits. I understand cancel pending messages and close all stacks, but I'll a little

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread Mark MacKenzie
@lists.runrev.com Date: Thu, 26 Oct 2006 14:31:01 EDT To: use-revolution@lists.runrev.com Subject: Re: Standalone app as Frankensteinian Monster Hi Mark Well, it looks like you are doing a lot of unnecessary stuff. If you want to 'quit', all pendingMessages will terminate and all stacks

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread Devin Asay
On Oct 26, 2006, at 2:34 PM, Mark MacKenzie wrote: I tried stripping things down to this script. Then after that wouldn't work I inserted a script to cancel pending messages, still no good. That leaves, in my mind, the question of running externals. Would having an opend connection to

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread Mark MacKenzie
Hello Devin. Not having much luck so far I stripped the close handler to the following: on closeStackRequest -- confirm whether to close the window answer question Are you sure you want to quit the entire program? with Yes or No if it is Yes then quit end if end closeStackRequest

Re: Standalone app as Frankensteinian Monster

2006-10-26 Thread Ken Ray
On 10/26/06 8:48 PM, Mark MacKenzie [EMAIL PROTECTED] wrote: Hello Devin. Not having much luck so far I stripped the close handler to the following: on closeStackRequest -- confirm whether to close the window answer question Are you sure you want to quit the entire program? with Yes