r6d2 wrote:Robert, have you ever experienced such a thing? And are you able to replicate it at will?
AFAIK Dropbox is clever enough to manage a change queue and do the things in the correct order to avoid this...
I believe I have experienced this, but no, I can't replicate it at will (yet). I am pondering a script that might replicate Scrivener's rapid-fire autosave (and a person's habitual invocation of File->Save keyboard shortcuts) to test out edge cases like this and tease out why some services (dropbox) work better than others (google drive, many others...). If I succeed in triggering this kind of conflict, I'll share my script & results for others to critique.
ScriverTid wrote:So, to put it in a nutshell, if I add a load of new stuff to Scrivener, I should pause Dropbox just before, then when I'm happy about what I've just pasted, unpause Dropbox? (And possibly make Scrivener's auto-save interval something fairly lengthy, e.g. like FileMaker's 5 minutes, to give Dropbox a chance to do its thing?)
I wouldn't go a whole 5 minutes. A lot of writing can happen (and be lost) if you have to wait 5 minutes without interacting with Scrivener. Note that the autosave interval is the amount of time that you have to leave a Scrivener project untouched, not the time between saves. I set my interval to 10 seconds, and haven't had any trouble since my last conflict. Note that I do not use File->Save (or the keyboard shortcut) at all, which could very well be the way some people trigger conflicts.