Standalone opens stack and then quits

Bill Vlahos bvlahos at mac.com
Thu Oct 14 00:32:08 EDT 2004


Great question Jeanne. I tried it and that stack doesn't quit.

Now my task is to find out what is being called in the stack with the 
problem. There is a handler in the stack script for closeStack but I 
commented it out.

What other messages could possibly be sent? Since this is with a 
standalone it will be difficult to monitor messages.

Bill

On Oct 13, 2004, at 12:49 AM, Jeanne A. E. DeVoto wrote:

> At 10:30 PM -0700 10/12/2004, Bill Vlahos wrote:
>> However, what I want to do is have the standalone give me the ability 
>> to select which stack(s) I want it to open. It does, in fact, open 
>> it, but then it immediately quits taking both the standalone and the 
>> stack down. I can't figure out why it is quitting. There is no quit 
>> stack command and it does correctly open the stack I select.
>
> Does it matter which stack you open? (If you create a blank stack with 
> an empty script, and open that, does this still happen?)
> -- 
> jeanne a. e. devoto ~ revolution at jaedworks.com
> http://www.jaedworks.com
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution



More information about the Use-livecode mailing list