Hi Everyone,
If a standalone LiveCode app in Windows has only one window open and the user
clicks the close box in the window, does this quit the app or is there still an
app menu from which the user must shut down? I ask because I develop on Macs
and do not have easy access to a Windows
The app quits. This is typical Windows behavior, and confuses a lot of people
switching from Windows to Mac. I cannot speak for going the other direction
because I have never seen a case where that actually happened. jab! ;-)
Bob
On Aug 31, 2012, at 8:54 AM, Gregory Lypny wrote:
Hi
Is there a way in LC to catch the action of the close button and
display a are you sure you want to quit message?
SKIP
On Fri, Aug 31, 2012 at 12:01 PM, Bob Sneidar b...@twft.com wrote:
The app quits. This is typical Windows behavior, and confuses a lot of people
switching from Windows to
Thanks Bob,
Much appreciated. Since I want to have my students log their signing out when
quitting, I guess I should determine how many windows are open at the time a
close box is clicked, and then assume that the intention is to quit if there is
only one.
Gregory
The app quits. This is
On 08/31/2012 07:01 PM, Bob Sneidar wrote:
The app quits. This is typical Windows behavior, and confuses a lot of people
switching from Windows to Mac. I cannot speak for going the other direction because I
have never seen a case where that actually happened. jab! ;-)
And this is also what
Hi Skip,
Am 31.08.2012 um 18:06 schrieb Magicgate Software - Skip Kimpel
s...@magicgate.com:
Is there a way in LC to catch the action of the close button and
display a are you sure you want to quit message?
catch the closeStackRequest message :-)
SKIP
Best
Klaus
--
Klaus Major
To be fair, some Mac apps do too. For some apps, it just makes sense. For some
it does not. What always got me about the Windows way was the fact that many
apps open as a window within which other windows open. So if you want to close
the inner window when it is maximized, you have to be
I haven't tested this in 5.5.1 but it used to be that closing the last
window in an LC standalone app on a Mac quit the application. There are
Mac Apps, usually simple utilities that only have one window, that do that
but I've found that the more normal Mac behavior is for the app to stay
open
The way to mimic the normal behavior of a Mac application staying open when the
last window is closed, is to have you main stack be a splash stack that remains
hidden the entire time, and you true application stack be an included stack or
substack. Create a menu for the mainstack so you can
Good suggestion, Bob. Thank you.
Gregory
The way to mimic the normal behavior of a Mac application staying open when
the last window is closed, is to have you main stack be a splash stack that
remains hidden the entire time, and you true application stack be an included
stack or
To be honest, I hate the idea of splash stack/main stack unless there's a
valid user related reason for a splash stack. It just complicates the
application stack structure and, if I'm not mistaken, only the splash stack
is compiled when you create a standalone, the other stacks being right
there
True enough, but password protecting the other stacks encrypts the code in
them, so I am not sure what the risk is. I suppose to prevent the stacks from
being used by themselves, you can add some code in preOpenStack that checks
what the parent stack is.
Bob
On Aug 31, 2012, at 2:10 PM,
On 8/31/12 4:29 PM, Bob Sneidar wrote:
True enough, but password protecting the other stacks encrypts the
code in them, so I am not sure what the risk is. I suppose to prevent
the stacks from being used by themselves, you can add some code in
preOpenStack that checks what the parent stack is.
Yes, it's kinda the general untidiness of the splash stack approach that
gets to me. One compiled file is much better untless there's a really
compelling reason why you can't do that.
Pete
lcSQL Software http://www.lcsql.com
On Fri, Aug 31, 2012 at 2:54 PM, J. Landman Gay
On Aug 31, 2012, at 3:54 PM, J. Landman Gay wrote:
On 8/31/12 4:29 PM, Bob Sneidar wrote:
True enough, but password protecting the other stacks encrypts the
code in them, so I am not sure what the risk is. I suppose to prevent
the stacks from being used by themselves, you can add some code
The really compelling reasons for me is properties, and certain limits placed
on a compiled app. I got into the habit of using properties to store
information from session to session, and since a compiled app cannot be
modified, I cannot do that. At least that is my understanding.
Bob
On
16 matches
Mail list logo
