Re: quitting is too complicated

2007-07-07 Thread Martin Blackman
On a similar note, when you close a substack in the development environment, why does Rev ask if you want to save the substack and all other stacks in the mainstack before closing ? Closing the substack doesn't close the main stack so is this not an IDE bug ?

Re: quitting is too complicated

2007-07-07 Thread David Bovill
I'd say it was from a user point of view - all though it may be a little tricky to get around as in some permutations the main stack may not get saved because it was not aware that a substack needed saving. It should be possible to flag this though. On 07/07/07, Martin Blackman [EMAIL PROTECTED]

quitting is too complicated

2007-07-03 Thread Björnke von Gierke
I seldom make applications, but I've run into these problems when I tried to make my first os x standalone this year: 1. command-q does never produce closestackrequest. 2. closing the stack does leave the application running (as long as there is any other stack in memory). Therefore I had to

Re: quitting is too complicated

2007-07-03 Thread J. Landman Gay
Björnke von Gierke wrote: I seldom make applications, but I've run into these problems when I tried to make my first os x standalone this year: 1. command-q does never produce closestackrequest. Right. CloseStackRequest is only sent when the user physically clicks the close box. It's the

Re: quitting is too complicated

2007-07-03 Thread Ken Ray
On Tue, 3 Jul 2007 22:21:37 +0200, Björnke von Gierke wrote: I seldom make applications, but I've run into these problems when I tried to make my first os x standalone this year: 1. command-q does never produce closestackrequest. No, and I think it may be a documentation issue -