1 person found this helpful
This used to happen to me a lot too with CS4.
I believe it is fixed/correct in either an update or with CS5.
Unfortunately, I believe your file is gone. Like any software, files are saved from memory, with memory issues, file gets corrupted or not saved, or similar.
So the best way you can deal with this, is to get backup in the future.
The bug made me change my workflow and it is something I suggest you do for the future:
- Each workday/major change to design, save the file as a new file, name it with a different date, so it is easier to find. I usually name them like this in a project folder: name_numberdateyear.png
- Get backup solutions. I use Dropbox and it is a lifesaver. My whole professional life is there, synced across several machines and backed up to a local NAS (Synology)
- Dropbox and several other solutions comes with version control, which has saved me from blunder caused by stress. Like saving over the wrong file. You can always restore a pervious saved and synced version. This renders my first step a bit old school and slightly over cautious
It is not a nice situation you got into, I feel sorry for it happening. But look at the bright side, you might find some new approaches to your design.
And do backups!
Yes normally I have an external hard drive that does dropbox backups every 10 minutes. As another failsafe, I had it saved to dropbox. But for some reason, I forgot to plug in my time machine drive.
Dropbox did have a version but it was like an hour old so it wasn't a complete loss. I just don't understand how Fireworks could delete a file from the filesystem.
Thanks for the advice and yes, when working in Fireworks from now on I am going to take extra steps to make sure this doens't happen. Thanks for the advice.
If that file was really important, you could try some data recovery software... I've successfully recovered files that I'd accidentally deleted this way.
When you trash files, they get removed from your system's file directory, so to speak, but they're still on your hard drive for a period of time... so I imagine your FW file might still be around. However, it sounds like you found a version to work from, so it's probably not worth the time it would take to explore this option.
Oh, I almost forgot to mention: You might want to take the time to run Disk Utility to give your hard drive a checkup (e.g., run the Verify Disk command).