Hi Susan,
It sounds as though you’ve found this already, but yes, on 10.7 and above, Apple hid the ~/Library folder for some reason. It’s there, but you have to use the Option+Go menu trick to get to it.
Ouch, sorry to hear you’ve lost work!
I can assure you that there is absolutely no way Scrivener could do this - there is no code that could possibly wipe out your text. To me, this sounds like an external issue. The fact that you were saving on Dropbox is most likely the culprit. Scrivener files re really packages - that is, a .scriv file is really a folder full of files that looks like a single file to the user in the Finder. All of the text files in a project are saved individually inside the .scriv project. To Dropbox, a .scriv file is just a folder. It is possible that if Dropbox causes a problem or encounters a conflict, it can rename the files in a folder. If it does this to a Scrivener project for some reason, it could make it so that the file names of the files inside the .scriv package are not recognised by Scrivener, so Scrivener won’t find them.
One thing to check, therefore, is the inside of the project. Please Ctrl-click on the affected .scriv file in the Finder and select “Show Package Contents”. This will reveal the internals of the .scriv package in the Finder. Then drill down inside the Files/Docs folder. There should be lots of numbered RTF files in there, each RTF file representing the text of a document in your project. If these have been renamed to have the date and/or your computer and user name (which Dropbox does on rare occasions when it finds a conflict because you’ve been trying to access the same files from two machines, for instance), that may well be the cause of your problems. Let me know and we can take it from there.
There’s no voodoo here - when you launch Scrivener, it simply opens the last files you had open. It cannot open a backup unless you opened the backup. So you must have opened the backup of the project instead of the original at some point, which is why it was from that point opening the backup and not the original. Scrivener cannot open a file automatically that it doesn’t know about - the files it opens automatically on launch are the ones you opened previously.
Yes, it does - the operative words there being “by default”. If you don’t choose a different backup folder or choose to turn the backups off, then obviously the behaviour will be difference. Please open the Backup pane of the Preferences (the Preferences can be opened from the “Scrivener” menu) to see what your current settings are. There it will tell you whether automatic backups are turned on and also which folder the backups are set to be saved in.
One thing to check is your system date - could something have gone wrong with that? Four years is a long time ago - Scrivener 2.0 wasn’t released until the end of 2010, so it’s unlikely that Scrivener 2.0 could have made automatic backups that are four years old. The dates of the backups are only as reliable as your system date, though, which is why I say to check that.
Like any program, Scrivener saves documents to the location you chose for them. When you create a project in Scrivener, you are asked to choose a location for it to be saved - you must have created a folder in Dropbox for Scrivener files and have chosen to save your project there. That is the only reason your project would be saved to such a location. And as I say, I think a Dropbox issue may be at the heart of all the issues you are experiencing.
This isn’t actually possible. Scrivener can only open the files that were open the last time it was used - it cannot open anything automatically that wasn’t opened by the user. It certainly can never make a backup and open that backup instead of the original - it’s just not possible given what Scrivener is capable of. So something else must be happening here, although it’s difficult to say what without more information.
The first thing to try is to look at the inside of the project in Dropbox to see if the text files have been renamed by Dropbox, as described above. Also check the location of your automatic backups folder (and that backups are turned on), as also described above. Let me know how that goes and we can take it from there.
All the best,
Keith