Re: unexpected quit on closeStackRequest
>ROB: >FWIW, your handler runs fine on Mac OS 9. One thought: >closeStackRequest should be speciific to the stack whose close box is >clicked on: I see no reason to pass it. > >KURT: >Thanks for testing the script, Rob. However, if I comment out the line: >pass closeStackRequest Your're right, Kurt, I now realize all my closeStackRequest handlers either call a shutdown handler or include "close this stack"; so I've never passed the message. -- Rob Cozens CCW, Serendipity Software Company http://www.oenolog.com/who.htm "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: unexpected quit on closeStackRequest
Hi Kurt, I often get an 'unexpected quit' message on OSX, even when I quit an application legitimately. It also happens with the rev development environment. I thought it was a bug in OSX. I just shout at the computer "It was NOT unexpected!" and move on. mark mitchell Japan ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: unexpected quit on closeStackRequest
> ROB: > FWIW, your handler runs fine on Mac OS 9. One thought: > closeStackRequest should be speciific to the stack whose close box is > clicked on: I see no reason to pass it. > > KURT: > Thanks for testing the script, Rob. However, if I comment out the line: > pass closeStackRequest > > in the above script, the stack does not close after deleting the temp > file. > Perhaps the Rev editor has to do some stuff which it doesn't get done if > the closeStackRequest is not passed? Curious. This is one of this cases where passing a system message is more than just a good habit, and instead directlt affects behavior: trapping closeStackRequest without passing stops the request -- the stack does not close. To close the stack, pass the message and the Rev engine will complete the request. -- Richard Gaskin Fourth World Media Corporation Custom Software and Web Development for All Major Platforms Developer of WebMerge 2.0: Publish any Database on Any Site ___ [EMAIL PROTECTED] http://www.FourthWorld.com Tel: 323-225-3717 AIM: FourthWorldInc ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: unexpected quit on closeStackRequest
from the docs Handle the closeStackRequest message if you want to prevent a stack from being closed. Notes: If the closeStackRequest handler does not pass the message or send it to a further object in the message path, the stack does not close. Passing the message allows the stack to close. ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
Re: unexpected quit on closeStackRequest
>The following causes a (repeatable) unexpected quit (according to >Mac OS X) only when run from within a stack, not as a standalone: > >on closeStackRequest > answer "This will close this application." with "Cancel" or "Close" > if it is "Cancel" then exit to top > else > if there is a file "tempfile.txt" then > delete file "tempfile.txt" > end if > pass closeStackRequest > end if >end closeStackRequest Hi Kurt, FWIW, your handler runs fine on Mac OS 9. One thought: closeStackRequest should be speciific to the stack whose close box is clicked on: I see no reason to pass it. -- Rob Cozens CCW, Serendipity Software Company http://www.oenolog.com/who.htm "And I, which was two fooles, do so grow three; Who are a little wise, the best fooles bee." from "The Triple Foole" by John Donne (1572-1631) ___ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
