I'm *sure* I saved

[low_delta]

That same part I worked on yesterday afternoon. Apparently, I never saved it again, after that. Again, I swear I saved it multiple times. I mean, like, saved it, closed it, reopened it, worked on it, saved it, worked on it some more. And made sure I saved it before closing for the day.

This is pissing me off.

Comments

[marswalker.livejournal.com]

That's a feature of windows... it's saving you disk space.

In Unix, my favorite editor is VI - it supports a command called "autosave" - even if the system crashes while you're editing, it'll do it's best to save a copy of the "temp file" for recovery later. It's just a plain-text editor, though, doesn't do all the bells-and-whistles that Word (etc) do, but then... it works.

[low-delta.livejournal.com]

This is Pro-Engineer. There is no autosave. It doesn't even prompt you to save when you close. You get into the habit of saving before you close. That's why I have a hard time believing I never saved. Espeically after the first time I lost work yesterday.

The reason it doesn't do autosave, is because each time you save your work, it saves a new file. They numbered, and when you open the part it opens the highest number of that part. The reason it works this way is so that if you have trouble, you can go back to an earlier version. Autosave would be trouble, because you wouldn't be able to keep track of what changes were made and when. Besides that, when you're in the middle of a feature, it can't save. And sometimes when you get done with a feature, you don't want to save. The average windows user would have trouble with this sort of setup, but I prefer not to rely on automatic actions.

[marswalker.livejournal.com]

That sounds a bit like the old built-in CMS / VMS editor - every time a file is edited, the old version is saved to a numbered version.

For important files, I use CM-tools, you have to "check-out" a file before you can edit it, and when you're done, you "check-in" the file. If you make a bad mistake, you "un-check-out" the file, and it reverts to the state it was in before you last checked it out.

but yah, I understand about getting into the habit of doing a save-exit (or write-quit), vs just "exit".

It's possible that you did save it, and the actual "save" wasn't flushed out to the file system somehow. And being human (I trust you are.... :-) ) it could even be possible that the "save" part slipped. That's frustrating.

[low-delta.livejournal.com]

Been getting a lot of glitches lately, but I've never heard of a save not going through.

[low-delta.livejournal.com]

So, today...

My directory was looking ugly, so I purged it of all the earlier versioned files in it. I didn't find out until later that one of my parts had unwanted changes saved to it. I spent nealy two hours trying to fix it, and might never get it working right again. All because I purged without checking what I might be losing.

[marswalker.livejournal.com]

I've done that, and felt pretty dimwitted for having done it. I felt a lot better when one of the rocket scientists at JPL called a bunch of us to the lab to show us a small problem - and he couldn't because he accidently deleted the working version of his software and altered the back-up to where it no longer worked at all. You're in good company.
I know that probably doesn't help with the frustration...