Referencing a stack that is not open

David Bovill david at openpartnership.net
Fri Jul 13 19:59:32 CDT 2007


It loads the stack into memory and keeps it there. You will see this if you
check the "mainstacks". This is not the same as an "open" stack which you
can check using the "openstacks".

Every time Rev gets a property (even if it checks whether a stack exists) it
"loads" the stack into memory - you have to "unload" it using the very badly
named "delete stack" syntax if you want to be picky about memory.

In practical terms there is not much difference between an open stack that
is not visible and a "loaded" stack that is not open.

Hope that helps :)


On 14/07/07, Dan Friedman <dan at clearvisiontech.com> wrote:
>
> Hello!
>
> Can anyone tell me what exactly happens when you ask for information about
> a
> stackfile that is not open?  For example, say on your desktop you have a
> stackfile named "testStack.rev" and you call this:
>
> put the customKeys of stack "/Users/Jimbo/Desktop/testStack.rev"
>
> Rev WILL report the correct data.  However, the stack doesn't appear to
> have
> actually been opened.  What actually happens?  Did Revolution read the
> entire stack file, get the requested data, then flush it from memory?  Did
> it read only what it needed?
>
> Any insight would be appreciated.
>
> Dan
>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>



More information about the use-livecode mailing list