Yesterday I lost around 5 hours of my work because vvvv completely messed up 4 of my main patches and its xml backups. while this is completely unacceptable, this happened to me for the second time now (not counting the ‘normal’ xml glitches that renders a file unaccessible), so I am looking for a workaround solution that prevents the loss of files in the future. I hope there are a few Windows wizards out that could help me on any of my ideas:
- using Dropbox
They create a version everytime you save a file and keep it for 30 days on the Pro plan. I think that’s the easiest solution but it costs 99 usd a year and I don’t really need the other Pro features plus I don’t wanna work inside a Dropbox.
- 3rd party tool
Somebody knows if there is a tool that (like Dropbox) automatically saves every saved version of a file into a (local) database or something? that would be a very nice solution.
- Windows/Previous Versions
Is there a way to force Windows to create a ‘previous version’. (I don’t know how this feature is called but you can find it in the Properties tab of a file in Windows Explorer). It seems completely arbitrary to me when Windows chooses to automatically create such a version. If vvvv could tell Windows to create a new version when saving a patch that would be very helpful, it would also mean to get rid of those ugly ~.xml files.
I got every project in git. Is there a way to create a cron job that inserts every file change into git on an predefined interval? Everything is a commit in git right? So it would mean to ‘amend commit’ every file change with a ‘autosave’ message. Or is there another git solution?
any hints appreciated.
ps: Why isn’t vvvv validating the file that belongs to a patch after it saves it (trying to read it)? If validation fails, there should be red flags all over the place (plus: ugly ~.xml files would be unnecessary).