Apparently my overall settings .cfg file gets corrupted occasionally, at some point before or during crash of 010 Editor, such that when I restart 010 Editor, and repeat what I was doing when it crashed, it will crash again.
Also, today while I was having problems with 010 crashing, I exported my settings.
After the next crash, I tried to import that .cfg file, but 010 told me that the file couldn’t be imported.
So here are a few thoughts on how to improve the user experience when there are problematic cfg files:
- Use a filename “tag” of some kind, like an incrementing field, to indicate earlier cfg files. This would make it easy to go back to a valid, earlier export of the settings.
- Tell the user why a requested .cfg file can’t be imported, for example: “File is incomplete”, “Setting ‘x’ is corrupt”; or if it’s failing something like XML parsing, show the item that failed.
- Document the format of the .cfg file.
- Validate the .cfg file before writing it. (If it contains XML, there might be an easy, safe way to test its validity? I don’t know very much about XML though.)
And of course, you may be able to think of better ways to deal with corrupt cfg files