correction: shutDownRequest HANDLER fails to work

[Thierry Arbellot]

Hi Barry,

I use the shutdownRequest handler in my app (OSX 10.2.6, Rev since v 
2.0) and it does work fine every-time.

I put the handler in the main stack, to be sure to intercept the Quit 
command from any substack.

Regards.

Thierry.

On Thursday, September 4, 2003, at 07:02 PM, Barry Levine wrote:

> I'm re-posting this because of an inaccuracy in the subject -AND- 
> add'l information.
>
> I have an OSX (10.2.6, Rev 2.0.2) stack that, when part of an app, is 
> using the following handler in the stack script to intercept the Quit 
> command:
>
> on shutDownRequest
>   if the platform is "MacOS" then
>     answer information "Are you sure you want to quit?" \
>     with "Quit" or "Don't Quit"
>     if it is "Quit" then pass shutDownRequest
>   end if
> end shutDownRequest
>
> The first time I select "Quit" from the app menu this handler is 
> called and I can cancel the Quit. However, the next time I select 
> "Quit" from the app menu (during the same session), the app just quits 
> without the intervening dialog. The Rev engine seems to be ignoring 
> the handler after the first time it is called.
>
> I have the same app in a Windows build. In that app, the handler shown 
> above is commented out and I rely upon the File menu's "Quit" command 
> which I have intercepted with a dialog, as well. In that case (WinXP, 
> Rev 2.0.2) canceling the Quit confirmation dialog always works 
> properly.
>
> Thanks,
> Barry
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>