Maybe this is already in Scrivener, and I’ve missed it. (I’m sure Maria or Amber will jump in with the answer, if so )
But I’d like a way to lock the binder so that documents could only be shuffled if I unlocked it first (similar to the way you can lock a document when you’re messing with the binder). The lock should persist from one usage of Scrivener to the next. My fear (and this has happened) is that I’ll carelessly be selecting a file or files to drag from the binder to the references and I’ll get everything out of order. Then, as clumsiness seems to breed more clumsiness, my attempts to move things back shuffles the documents even more. (Of course, cursing ensues.)
In the meantime, I’ve numbered all of my documents, but for the future…
Added to the “Future” list - that is the 1.5 - 2.0 list that won’t get looked at for a few months. Nice idea, but it won’t make 1.0, in other words.
Thanks,
Keith
I like it, but I think I would like it even more if it were selective instead of all-inclusive. That is, if I could select one part of the Binder, and it would lock everything below that point, leaving the rest free.
Is this still on the “someday” list (since 2007)?
Some of my Scrivener projects are relatively mature and I’d like to be able to “lock” binder structure and also file content. This would be to prevent inadvertent (careless) damage. I create named backups at the moment but that only applies to the entire project. I’d like a smaller granularity of control. (Snapshots help in saving file content but not with binder structure.)
Thank you for your consideration.
I think the fact that there is a thirteen year gap between that statement, and your question, is a pretty good indication as to its status on any lists.
Ultimately this is what backups are for, and it’s not too difficult to compile out an indented list of titles from a backup and compare it with what you’ve currently got, if you suspect your trackpad went nuts one day or something. An approach that protects you from an inconceivable quantity of potential mistakes is generally better than very specific software-imposed guardrail that only prevents against one possible mistake.
I should add there is also another mechanism that I use for projects that are complete, and that I want “frozen”, and that is to .zip them and delete the project once zipped. If I ever need to reference it in the future, I simply double-click on the .zip to extract a perfect copy of the project as it was frozen. When I’m done referencing it, I delete it. Every time I unzip, it comes out just as I left it the last time.
)
