Good idea, thanks Jacque.
On Fri, Jan 20, 2012 at 10:06 PM, J. Landman Gay
jac...@hyperactivesw.comwrote:
On 1/20/12 11:57 PM, Pete wrote:
The problem is, I want toc lose the stack but leave the application
running. If I pass closeStackRequest, I believe the app will quit
(Standalone) and
Hi Pete,
This is correct behaviour. You'r be very surprised if you close the last window
on Windows and your app continues running but is completely inaccessible. You'd
also be surprised of your standalone behaved differently on Mac. Moreoever,
without a window, you need a menubar with a Quit
If you take the splash stack approach and hide the splash stack before
launching the actual app stack, it won't do that. But you would have to have
some way of launching the app stack again, like a system menu in the splash
stack.
Bob
On Jan 19, 2012, at 10:25 PM, Pete wrote:
It seems
I have to respectfully disagree Mark, this isn't correct behavior.
Haven't used Windows for a long time but one of the major differences
between it and OS X is that there is a system menubar at the top of the
workspace on a Mac, not at the top of every application window. So you can
close all
On 01/20/2012 11:23 AM, Pete wrote:
As far as I can tell, all Mac applications work this way..
This is not correct. It depends on what kind of application it is. Most
work this way but several utilities do not. I have seen some discussion
of this elsewhere, although I can't recall where,
System Preferences is an example of an app that quits when you close the window.
On Jan 20, 2012, at 12:53 PM, Warren Samples wrote:
On 01/20/2012 11:23 AM, Pete wrote:
As far as I can tell, all Mac applications work this way..
This is not correct. It depends on what kind of application
On 1/20/12 11:23 AM, Pete wrote:
As far as I can tell, all Mac applications work this way. Closing the last
open window in the app and quitting it are two different activities. Even
the Livecode IDE works that way on a Mac.
Apple says that if your app has only a single window and is a
Hi Pete,
I think I already explained that you can use the closeStackRequest message.
There's also the shutdownRequest message.
--
Best regards,
Mark Schonewille
Economy-x-Talk Consulting and Software Engineering
Homepage: http://economy-x-talk.com
Twitter: http://twitter.com/xtalkprogrammer
On 1/20/12 2:00 PM, Pete wrote:
Thanks Jaccue. So I can't use a closeStack or shutdown message handler to
control this?
Pete
Old habits die hard so I've always used the dummy stack method. But now
that you mention it, yes, I think you could trap the closeStackRequest
message. That would be
OK, thanks Mark and Jacque. It sounds like the shutdownRequest message
will do the job - if I don't pass it, the application should stay open.
I'll have to figure out how to deal with the user selecting Quit from the
Application menu, or the user shutting down their computer since I really
do
On Fri, Jan 20, 2012 at 7:39 PM, J. Landman Gay jac...@hyperactivesw.comwrote:
On 1/20/12 4:00 PM, Pete wrote:
OK, thanks Mark and Jacque. It sounds like the shutdownRequest message
will do the job - if I don't pass it, the application should stay open.
I'll have to figure out how to deal
On 1/20/12 11:57 PM, Pete wrote:
The problem is, I want toc lose the stack but leave the application
running. If I pass closeStackRequest, I believe the app will quit
(Standalone) and if I don't pass it, the window will stay open, neither of
which is what I need to happen. But maybe I can
It seems that when you close the main stack window in an LC standalone
application on OS X, the application terminates. That doesn't seem like
normal behavior for an OS X application, at least not the ones I'm familiar
with. Maybe there's no right or wrong on this and it's a function of the
13 matches
Mail list logo
