The feature is for a beta error, but it's quite possible that it might occur for some other reason (e.g. damage to the SD card). As MRCC is critical piece of setup, it must be unbreakable.
If MRCC cannot start due to a default configuration load/interpretation error, then let it start with an empty setting, such as factory or specially created (read-only) "Safe mode". If MRCC does not start and hang, it will be much worse than if it starts with the recently removed setting.
In addition, you could do from time to time an automatic backup of settings (not visible to the user) that could be loaded during an error.
Going forward, you might think about versioning the configuration... It's pretty simple to implement (like everything, hahah
. But logically it could look like this:
- When saving a setting, it will be saved with name e.g. init01.xx.ini, where the name is the name of the setting and the number xx is the next number or date. Only the name init01 would be visible to the user.
- when uploading the setting init01 would always be uploaded version with the latest number xx. You wouldn't see all the versions. Nothing would change in the current upload settings.
- The only addition would be the option "load previous version" and when you click on it, all versions (only for init01) to choose from would be shown.
- when uploading settings and encountering an error, MRCC could automatically upload an earlier version.
If MRCC cannot start due to a default configuration load/interpretation error, then let it start with an empty setting, such as factory or specially created (read-only) "Safe mode". If MRCC does not start and hang, it will be much worse than if it starts with the recently removed setting.
In addition, you could do from time to time an automatic backup of settings (not visible to the user) that could be loaded during an error.
Going forward, you might think about versioning the configuration... It's pretty simple to implement (like everything, hahah
. But logically it could look like this:- When saving a setting, it will be saved with name e.g. init01.xx.ini, where the name is the name of the setting and the number xx is the next number or date. Only the name init01 would be visible to the user.
- when uploading the setting init01 would always be uploaded version with the latest number xx. You wouldn't see all the versions. Nothing would change in the current upload settings.
- The only addition would be the option "load previous version" and when you click on it, all versions (only for init01) to choose from would be shown.
- when uploading settings and encountering an error, MRCC could automatically upload an earlier version.