The problem is the same for the apple event.
BTW - The problem I am experiencing with the force-quit being necessary when compiling my app in OSX -for- OSX is gone with I compile on WinXP -for- OSX. I'm in the process of wiping a HD for a clean OSX / Rev install and will report if this resolves the problem. I can, however, generate a small app (on OSX -for- OSX) using a new 3-stack structure without the force-quit issue being present. There is something about my "problem app" that the OSX Rev IDE doesn't like.
There really is only one problem although it seems it can be exhibited using a number of methods: Rev is not disabling the Quit menu item when it is appropriate to do so. Everything else about this problem (the force-quit issue I am experiencing, the necessity to trap for the shutDownRequest or AppleEvent, etc.) is brought about by what is probably one or two missing lines of code in the engine.
Now, there is one additional issue -but- it would not be a problem if the first one didn't exist: You can't disable the Quit menu item in OSX. This tells me that the issue discussed in the previous paragraph is really the issue because, if that problem did not exist, we wouldn't be looking for a means to disable the Quit menu.
Regards, Barry
On Tuesday, Sep 9, 2003, at 05:33 America/Denver, Alex wrote:
shutdownRequest is also coincident with an apple event that's described in the docs. I would check to make sure that the apple event has the same bug as the shutdownRequest (gets sent during modal dialog). If the apple event for some reason doesn't suffer the same bug then that opens up a better workaround possibility.
_______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
