Looking for tips on memory mgt in standalones

[Peter Haworth]

Hi Tom,
Closing a stack still leaves it in memory as you found.  The delete stack
command will remove it from memory as long as the stack you name is a main
stack; for substacks, it literally deletes the substack.

And yes, you'll have the issue with your prefs substack.  I have taken to
storing my prefs in a flat file in different locations depending on
platform.

OSX: specialFolderPath("Home")/Library/Application
Support/<appname>/<prefsfilename>

Windows: specialFolderPath(26)/<appname>/<prefsfilename>

Linux: specialFolderPath("Home")/<appname>/<prefsfilename>

If you have several products, you can optionally include a <companyname>
folder before the <appname> folder.
Pete
lcSQL Software <http://www.lcsql.com>



On Thu, Dec 6, 2012 at 12:16 PM, tbodine <lvhdgc7 at gmail.com> wrote:

> 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
>