I have encountered this as well--dating back to v 1.0, although I have been ascribing it to my inability to conceptualize how Rev handles stacks vs stack files in memory. To me the whole issue of memory purging (or non-purging) is probably the single most frustrating problem with Rev--mainly because I am having trouble figuring out whether my actions are the problem or whether Rev is"'at fault."
Sometimes I just purge then quit out of Rev, restart and then check Application Overview just to make sure everything is gone. Thanks, Richard, for putting into encapsulated form the problem I've been trying, albeit not always successfully, to work around. A specific request for the RunRev folks: I would find it immensely useful to be able to have all of my stack files have a main stack with the same generic name (for example MainApp) and have Rev not appear to get confused when I try to go from one stack file to another--as Richard set forth. Is this possible? Or is it already there but I'm making some sort of error and not getting setting things up the way they should be? Marian (PS sorry if my post is not as detailed as it should be but I've had no time to work with Rev in the last 2 months so details escape me.) -----Original Message----- From: "Richard D. Miller" <[EMAIL PROTECTED]> Date: Fri, 11 Jan 2002 12:52:47 -0500 To: <[EMAIL PROTECTED]> Subject: Some kind of memory/purge error > I'm encountering several problems with proper purging of stacks. Here's the > simplest example: > > I have several stacks open (some are substacks). > I close one stack (which has the destroystack and destroywindow commands in > it) > I check the revloadedstacks function and the Application Overview...both > show the stack as being purged. No sign of it. > I go to open a different stack which has the SAME stack name (but a > different file name). > I immediately get a dialog box asking what I want to do with the previous > stack (i.e. which has the same stack name). > > This appears to be some kind of bug in the program. It is causing an > inability to properly purge stacks from memory, as I'm continually opening > and closing numerous stacks but some are not being fully purged. Obviously, > it doesn't take long before I've got a serious memory problem. > > Is there a workaround for this, and has anyone else encountered it? Is this > a known bug? > > Thanks. > Richard Miller > > _______________________________________________ > use-revolution mailing list > [EMAIL PROTECTED] > http://lists.runrev.com/mailman/listinfo/use-revolution > -- _______________________________________________ use-revolution mailing list [EMAIL PROTECTED] http://lists.runrev.com/mailman/listinfo/use-revolution
