Don't you have to send "close me" in time? How do you close a stack with a
running script?
Bob S
> On May 15, 2018, at 24:28 , AndyP via use-livecode
> wrote:
>
> This is my go-to routine for quitting applications which seems always to get
> the job done.
>
> //General quit routine
>
> on
This is my go-to routine for quitting applications which seems always to get
the job done.
//General quit routine
on quitMyProject
lock messages
-- stop using stacks
put the stacksInUse into myStacks
repeat for each line myStack in myStacks
stop using stack myStack
end repeat
I wish LiveCode, Ltd would add a counterpart to revLoadedStacks() called
revUnloadStack that would do ALL the steps needed to really
close and remove a stack from memory
i.e it would set destroyStack to true, cantDelete to false, detect if it
was the stack containing the running script and if so,
It's the stacks in the STANDALONE that are still open I believe. I think this
because at one point there was an LC version that was confusing the source
stack and the standalone stack, and as a result it was overwriting my
stackfiles in the source stack with the locations of the standalone files
NEVER MIND
"Delete stack" is the answer. I should have known. I just wasn't
associating "Delete" with "removing from memory"
On 5/14/2018 3:19 PM, Paul Dupuis via use-livecode wrote:
> I know this has been discussed before, so my apologies that my Google-Fu
> has failed to find any prior answer.
I know this has been discussed before, so my apologies that my Google-Fu
has failed to find any prior answer.
I have a complex script - part of an Installer "maker" written in
LiveCode - that creates stacks and builds them into Standalones for
various platforms via a long automated script. After t
s
> _
> InfoWallet (http://www.infowallet.com) is about keeping your important
> life information with you, accessible, and secure.
> lcTaskList: (http://www.infowallet.com/lctasklist/index.htm)
>
> On Aug 4, 2012, at 5:14 PM, Peter Haworth wrote:
>
> > Unles
at 5:14 PM, Peter Haworth wrote:
> Unless I'm missing something, closing and removing a stack from memory does
> not trigger a closeStack message. That seems really strange to me but be
> that as it may, is there some other message that can be used to trap when
> that happens?
>
Unless I'm missing something, closing and removing a stack from memory does
not trigger a closeStack message. That seems really strange to me but be
that as it may, is there some other message that can be used to trap when
that happens?
Pete
lcSQL Software <http://www.l
