purging a stack: the third way has been found

[Jim Lyons]

Richard Gaskin wrote:

> There are two ways Transcript can purge a stack from memory: setting 
> its
> destroyStack to true and then closing the stack, or using the "delete
> stack" command.
>
> In more than a year and a half RevNet has had only four users which 
> have
> reported anomalies suggesting that the GoRevNet plugin is being purged
> from memory, but this could not be reproduced here and in most cases 
> the
> issue had mysteriously gone away.

One thing I haven't understood about the way this works is why it's 
necessary to close the GoRevNet stack. Why can't it be kept open and 
hidden, and only closed when RevNet is closed? I confess to having very 
little experience with using a library arrangement like this, or 
changing the frontscripts and backscripts for my purposes so far. But I 
am trying to learn about this now since my ideas are getting more 
ambitious. Thanks for all the inspiration and ideas you provide us, 
Richard.

Jim Lyons