dMZX Forums: Backups to subdirectory -> Archived Requests -> Tracker

Originally: Making backups to subdirectory fails with error

# How many backups to be made. Set to zero to disable backups.

backup_count = 32

# How often (in seconds) backups should be made

backup_interval = 10

# The name of the backup file. If you choose "backup" with 3 backups
# the backups will be named backup1.mzx, backup2.mzx, and backup3.mzx.

backup_name = backup/backup

# The extension of backup files (keep this .mzx if you want to be able
# to easily load them)

backup_ext = .mzx

I think there should probably be a separate option for backup_subdir perhaps, and an attempt to create the directory if it doesn't exist.

The error itself is an "Error saving world" dialogue that pops up whenever it tries to save, due to it being unable to find the subdirectory.

Is it really useful to save backups to a different directory? All but the simplest worlds will have code that uses files in the directory above the backup directory, so loading the backup directly in the editor won't work properly. You end up having to copy the file back to the upper level before using it.

I don't think backup_subdir is necessary. Your trick of pre-pending a directory name in backup_name can be made to work.

--ajs.

Well, considering this issue was indirectly brought on by Guy accidentally overwriting one of his MZX projects with another, this is less of something that would be ran in the subdir and more of something to prevent egregious PEBKAC errors.

Yeah, the subdirectory field was just kind of a random thing I threw out, but what's great about using a subdirectory is

1) no backups cluttering the main directory when you don't want them to
2) harder to accidentally do work on a backup and realize it 15 minutes later
3) easier to exclude backups from a game submission
4) easier to have half a hundred backups and still find your game .MZX file in the load dialog.

So yeah, the only real changes would probably be just to say in the config file that you can do it, and then to make it create directories that don't exist when it goes to save the backup.

I should clarify my opinion on this: I think the proper fix is to have MegaZeux attempt to create the subdirectory if it doesn't exist.

Updating status to: Awaiting Feedback

Moving to: MegaZeux Feature Requests

Updating status to: Approved
Updating severity to: 1 - Low
Updating version to: 2.84


I'm going to implement this one at the same time I remove chdir(). Don't be surprised if it gets pushed back to 2.84b.

Updating version to: 2.84b

Updating status to: Implemented
Issue fixed in: GIT

Implemented in GIT master/9cc746b. MegaZeux will now attempt to create the entire backup path if it doesn't exist.

Moving to: Archived Requests