Comment 1 for bug 1813475

I agree with your findings and reasoning.

Thinking about how to implement this, this idea crossed my mind.

We have to implement:
- a configuration versioning schema numberering: to keep it simple, we could use the Xpad version number.
- a lookup table which elements in the configuration file correspond with which version of Xpad. This gives us the possibility to upgrade the configuration file by adding new items (for example first_pad_color_default) and to remove obsolete/deprecated items.
- a automatic validation and upgrade/downgrade of the configuration file up-triggered on Xpad application startup.

I bet there is existing code for this which we can use as a base.