Standalone opens stack and then quits

[Bill Vlahos]

Thanks to Geoff Canyon for the answer. The stack I was opening had an 
ask dialog box which comes up immediately. I had used the automatic 
detection of inclusions. The ask and answer inclusions were not 
included automatically because my standalone didn't call them.

Setting it to manual and including them solved the problem.

Tip of the derby to Geoff and the other folks who helped.

Bill Vlahos

On Oct 13, 2004, at 9:32 PM, Bill Vlahos wrote:

> 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
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution