We include that deliberately because we have gotten the exact opposite feedback from some users -- they expect a list of all the versions and need to count backwards one or two or N. It's meant to help orient you.
Given that these are exactly opposite requests, I don't think there's a way to accomodate both positions.
I've gotten used to use this as a shortcut to do a save of the full hierarchy...(perhaps I'm not alone...(?)).
I could still use it like that of course even if the current version was removed, but then it would require an upconversion afterwards, and introduce possible backwards compatibility issues.
Mads, what did you mean by "upconversion afterwards"?
If you Save for Previous with the purpose of simply duplicating the entire hierarchy like he explained (as opposed to actually watnting to use the copy in the previous version), then when you open that hierarchy in the original version it needs to Upconvert from the previous version it was just saved for.
Having the current version in the Save for Previous list eliminates the need for the upconversion when using the tool to duplicate the hierarchy.
I like having the current version for the reason Mads said. Even if you have some code in a re-use library or in instr.lib, it will save it all with the proper hierarchy and you can run it on a different computer easily.
Kidlin's Law -If you can write the problem down clearly then the matter is half solved. -----------------------------------------------------------------------------------------------------------------
