On Sun, 16 Jul 2000, Sivakatirswami wrote:
> Aloha,
>
> Opening downloaded a closed stack in memory (i.e. not destroyed) that was
> downloaded but never saved to disk has some unusual behavior.
>
> Scenario:
> -- Boot Stack A,
> -- Button in Stack A downloads Stack "Portal" from the web
> -- Stack "Portal" has a button that downloads Stack C and then closes itself
> (but stack "Portal" is never saved to disk)
> -- We want stack C to auto open stack "Portal" when it closes
> According to documentation, Stack "Portal" is still in memory if not
> destroyed. . .
>
> But
> on closeStack
> open stack "Portal" #using the stack's filename
You'd want to use the stack name here, not the filename.
> end closeStack
>
> Doesn't open it. One could presume this is because it was never saved to
> disk and therefore has no path as such. Is there a way around this?
This isn't the problem. If you run "put the mainStacks" in the
message box, you'll see a line for that stack.
> Also I close stack "Portal" but not destroy it and then download stack
> "Portal" again, I don't get any message telling me that Stack B is already
> in Memory and if I want to purge the previous one or not. . .
>
> But then I solved the problem by
> a) not unloading Stack "Portal" after it arrived
> b) storing the hRef of the Stack "Portal" into a global gPortalhRef
> c) closing Stack "Portal"
> (one could also query the cachedURLs)
>
> Now, we can re-open stack portal anytime (assuming we never exit) with:
>
> global gPortalhRef
> on mouseUp
> go url gPortalhRef
> end mouseUp
>
> OK, fine, but can someone explain the two different behaviours in more
> explicit terms? Is there a way to go to the cached stack more directly? One
> would rather not have to globals or keep having to query the cachedURLs,
> although that is certainly doable if it is the only way. Is stack "Portal"
> in memory or not? Is the http "cache" in a different place in MC's heap
> space?
Yes.
> Or is it placed in a ram sector outside of MC's heap space? The
> second issue (besides direct access to open the stack from memory) being how
> far can you go with this before you better make sure you start unloading
> some URL's .
There's no point in keeping the cached version of the URL around once
you've opened a stack. You should "unload" the cached copy
immediately after opening the stack.
Regards,
Scott
> Hinduism Today
>
> Sivakatirswami
> Editor's Assistant/Production Manager
> www.HinduismToday.com
> [EMAIL PROTECTED]
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
Archives: http://www.mail-archive.com/metacard%40lists.best.com/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
