Versions

[losiledlighting]

How do you keep track of changes in Rev?
I frequently save different versions with a different name, but my stacks continue to have the same names so that my scripts all work. However, when I launch a different version of a project, Rev complains that several stacks have the same names. Do I have to rename all my stacks every time I save a slightly different version of a project? Can I completely remove a project from memory so that I can reload a related stack? I find it quite frustrating: the message asks: do you want to purge, save, or cancel, then keeps asking the same question over and over. I've tried several combinations and haven't found the one that just leaves the last project alone, and launches the new one as is.

[richmond62]

I keep track of changes in 2 different ways (depending on what
sort of mood I'm in that day):

1. Do each save into a date-stamped folder on my hard drive.

2. Save stacks with the date appended to both the name of the
file and the name of the stack it contains.

I do the second thing by popping a "Save" button the my stack
that will perform a save with an appended date.

And all that purge stuff makes no sense whatsoever to me; so I just get round it by doing #2.

[bogs]

I work in much older versions, but,

Can I completely remove a project from memory so that I can reload a related stack?

Yes you can, and quite easily from the project browser or menubar.

Close and remove before opening the same name stack from other version...

[jacque]

If you want to replace the copy in memory with the new copy you're opening, choose Purge. To avoid the problem entirely, do as Bogs says and remove the existing stack from memory first using the LC menu.

The default preference for new stacks is to keep them in RAM when you close them. You can change that in prefs so that all new stacks will be completely removed when closed. You can set existing stacks to use that behavior by setting its destroystack property to true in the stack property inspector. I always work with destroystack true to avoid the problem. On the few occasions when I don't want the stack cleared from memory I set the property for the stack to false manually.

[Klaus]

I have also experienced the "Save/Purge/Cancel" madness when simply doing "Save as..." with a stack. Of course not reproducable, but highly annoying!

[richmond62]

One way to avoid "the madness" is to rename your stack when you do a "Save as . . ."
-

[Klaus]

Why should I, if I only want to save the same stack under a new filename?
The madness should not happen at all!