As users upgrade from one version of CR_Documentor to the next, the way settings are stored (the format) changes, the number and type of settings change... and if there's some reason for the user to roll back to a previous version of the product, the settings load/save is not robust enough to recover from a settings read error.

The way user preferences are stored and loaded needs to be updated so, at the very least, if an error occurs some default behavior will take effect.

Ideally as the application updates, old settings should be removed so settings disk space won't be wasted.

Should there be some sort of "panic button" that force-resets all of a user's settings?

Should settings store some sort of internal version so we can keep compatibility information? Doing that might allow us to say "If the current settings version doesn't match the plugin version, perform an upgrade or rollback operation to ensure the system behaves correctly."

As part of this, the "Default Settings" button in the settings window should probably do the clear of any previous settings keys that aren't used anymore.

Note that this doesn't seem to be much of an issue, at least recently, since the set of settings hasn't really changed. If we switch what things are configurable, though, this becomes more interesting.

Closing this out since I don't think we really need to do anything. We can open a new issue if it becomes pressing.