AAARGH! Resolve just ate my project!

I was working on a project, and since I'm using the latest super-crashy beta, it crashed on me with unsaved changes. no prollem, it autosaved a couple of minutes ago, so I restore from the backup. So now in the project manager window I have "my original project" and "my original project.201806260123456". I work on the backup and save. All good so far.

Then I open up the project manager and decide that to avoid confusion I will delete the "my original project" item, so I just have the one I'm working on. Makes sense to not have two copies showing up, right? DO NOT DO THIS! For some reason this also deletes the backup copy, meaning that all my work is down the toilet. @Blackmagic, this is not the expected behaviour. Can you at least warn users that deleting a project will also delete downstream copies of it? It is very unintuitive UX design.

Well, I'd say a) don't do that.

B) project backups don't take up that much space. I do them all the time, and if it's a really important project, I'll manually export them twice a day.

The only time I ever, ever delete backup projects is once the project is delivered. Then and only then, I'll delete all but the last couple of backups. I'm on a feature now where I have 6 backups, one for each day I've been working, and I expect to be done tomorrow or the next day. So maybe I'll delete the backups after Friday or so.

Drive space is cheap. I'm not worried about filling up a large drive with DRPs, which are typically well under 1GB or so.

So I wasn't deleting the backup, I deleted the original, because I'd been working on one of the backup copies, and I didn't want to have two versions of the project appear in the project manager page—potentially causing confusion later on.

If you restore a backup copy of a file it appears as a separate project in the project manager. It shouldn't be deleted when you delete the original, that's just wrong.

[Rohit Gupta]

So I wasn't deleting the backup, I deleted the original, because I'd been working on one of the backup copies, and I didn't want to have two versions of the project appear in the project manager page—potentially causing confusion later on.

If you restore a backup copy of a file it appears as a separate project in the project manager. It shouldn't be deleted when you delete the original, that's just wrong.

Hi Stephen,

We are not seeing this behaviour here. Could you please just make a test project, let it backup a couple of times, restore the backup, and then delete the original test project? Please see if you can reproduce the issue.

@stephan Well that depends . Dont know how it is implemented but for example if backups are made using some sort of snapshotting/delta mechanisme then you should never delete the original. In unix that is common knowledge . Think of it as deltas on top of the original. Faster backups and smaller files if you just save deltas. But then dont delete the original or your deltas have no reference.
But you are very right if you say that if such a mechnisme is in place it should pop up in loud screaming warning signs if you attempt to delete the original.