Yes long standing issue ever since v9 I believe. Might have been since v7. I
have to do the same thing. Apparently copies of things like library stacks (not
the originals, but the COPIES created when building a standalone) are left open
in memory. Not sure why they do that. Anything opened in th
On Jul 26, 2019, at 3:40 PM, Bob Sneidar via use-livecode
wrote:
>
> K!
Don’t be scared.
Be *very* scared . . .
There is something wonky about the whole in and out of memory thing.
My project is (during development) a bunch of main s tacks, with an mcp
to rule them all . . .
K!
Bob S
> On Jul 26, 2019, at 13:25 , J. Landman Gay via use-livecode
> wrote:
>
> The word you want is "delete" but you will have to be careful. If you delete
> an open mainstack, it is purged from memory without saving, but the file
> remains intact on disk. However if you delete a s
are | http://www.hyperactivesw.com
On July 26, 2019 2:09:59 PM Paul Dupuis via use-livecode
wrote:
I know this comes up again and again, is there some counterpart to
"revLoadedStacks(application)" that can PURGE a stack from memory?
If you have a stack open, say stack "A"
I know this comes up again and again, is there some counterpart to
"revLoadedStacks(application)" that can PURGE a stack from memory?
If you have a stack open, say stack "A" and you open a different stack
file with a stack called "A", the IDE presents a message ab
