In my case, my second stack *was* a substack and quit still didn't work.
On Wed, Nov 11, 2015 at 9:42 PM, J. Landman Gay
wrote:
> That's what I suspected; the stacks aren't actually substacks. Now it
> makes sense. Thanks for the clarification.
>
> On 11/11/2015 10:59
The dictionary says this (from LC 6.7.5):
In standalones, some care is needed to ensure you receive the
*shutdownRequest* message if your application uses multiple stacks. The
most reliable approach is to install a library stack or backscript to
handle the message when your application starts up.
That's what I suspected; the stacks aren't actually substacks. Now it
makes sense. Thanks for the clarification.
On 11/11/2015 10:59 PM, Howard Bornstein wrote:
The dictionary says this (from LC 6.7.5):
In standalones, some care is needed to ensure you receive the
*shutdownRequest* message if
On 11/11/2015 7:54 PM, Mark Smith wrote:
is it not the case that the message path goes from substacks
to the main stack? If so, should not a "shutdownRequest" message not handled
in a sub stack be passed up the message path to the main stack? In which
case you don't need shutdownRequests in each
e 'pass shutdownRequest' command that
>> allows
>> the application to quit.
>>
>> Mainstack >card "main" script
>> ---
>> on preparetoquit
>> quit
>> end preparetoquit
>>
>> on shutdownRequest
>>
all of the code you want implemented
>> before
>> quitting. This handler has the 'pass shutdownRequest' command that allows
>> the application to quit.
>>
>> Mainstack >card "main" script
>> ---
>> on preparetoquit
>> quit
>>
; >> This shutdownRequest handler has all of the code you want implemented
> >> before
> >> quitting. This handler has the 'pass shutdownRequest' command that
> allows
> >> the application to quit.
> >>
> >> Mainstack >card "ma
the 'pass shutdownRequest' command that allows
> the application to quit.
>
> Mainstack >card "main" script
> ---
> on preparetoquit
> quit
> end preparetoquit
>
> on shutdownRequest
>
>
> pass shutdownRequest
> e