Looking for tips on memory mgt in standalones

[Jan Schenkel]

Hi Tom,

Set the 'destroyStack' property of the instance stack to true. That way it is completely removed from memory when it is closed.

HTH,

Jan Schenkel.
 
=====
Quartam Reports & PDF Library for LiveCode
www.quartam.com


=====
"As we grow older, we grow both wiser and more foolish at the same time."  (La Rochefoucauld)


----- Original Message -----
From: tbodine <lvhdgc7 at gmail.com>
To: use-revolution at lists.runrev.com
Cc: 
Sent: Thursday, December 6, 2012 9:16 PM
Subject: Looking for tips on memory mgt in standalones

Hi, all.  Two questions about standalones...

I'm building a desktop app as a standalone that will use separate stacks to
store the user's work. A "New File" button creates the stack under a new
name and saves it to the user's document area. When the user closes such a
file, it looks like it still persists in memory. (Going by what the
Application Browser shows.) What's the best way to remove these document
stacks from memory in a standalone? 

Also, the app will need to save user's preferences. Knowing that main stacks
cannot save to themselves, I set it up with a substack that stores prefs in
custom properties. However, I see now that the substack is actually part of
the main stack file. So doesn't that means the substack will have the same
problem of being sandboxed by the OS and unable to save? What solutions do
you recommend?

Many thanks.

Tom Bodine



--
View this message in context: http://runtime-revolution.278305.n4.nabble.com/Looking-for-tips-on-memory-mgt-in-standalones-tp4657895.html
Sent from the Revolution - User mailing list archive at Nabble.com.

_______________________________________________
use-livecode mailing list
use-livecode at lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode