Richard,
I'm having the same problem which is still present in DP 2.9 b2. I
believe there are a couple of BZ tickets on this including one Ken
Ray created with me. It is a real problem and one I have not been
able to solve.
Perhaps I can talk to you offline?
Bill Vlahos
On Nov 17, 2007, at 12:18 PM, Richard Gaskin wrote:
Björnke von Gierke wrote:
On 17 Nov 2007, at 18:28, Peter Brigham wrote:
This must be a common need, so I imagine that there are well-
established ways of handling it.
Yes it's a common need, but it's not documented, nor is there any
simple way provided build in. This and menu handling in general is
why I rarely ever make standalones at all.
Additional possible confusions arise when you quit an application,
but your shutdownrequest handler is not in the message path (for
example when there's a dialog opened).
FWIW, I just created a new stack, added a menubar, and built a
standalone, all using only Rev's default settings. The engine
responds to the OS' aevt/quit normally as expected, quitting the
app without issue.
The appleEvent handler is helpful if you need special behaviors on
quit other than just quitting, but it seems the engine does the
basics well on its own with nothing else required.
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
