should quit question

I just realized that when adding a ‘should quit’ handler to a project, the project doesn’t quit.
At first I thought it had something to do with the script not being able to exit the ‘on idle’ handler.
To test the problem I made a new project without any code except for connecting the ‘Files Owner’ to several different handlers.
The project quit as expected until I added the ‘should quit’ handler to the project.
There was no problem when using ‘on will quit’, so It’s not really a big deal.
I’m just wondering if this is a bug or is there a reason the should quit handler works this way?

Browser: Firefox 3.0.3
Operating System: Mac OS X (10.4)

Your should quit handler needs to return true to allow the application to quit (see the documentation). Maybe if you did not return any value it is interpreted as false, thus preventing the application from quitting.

If you just want to do some things before the application quits, but do not need to ability to cancel the quit operation, then will quit is the better choice.

I see. It’s like a ‘safety net’ to make sure certain conditions are met before it lets you quit the app.
That may come in handy in a future project. Thanks for the info, Chrys. Merry CHRISTmas