Ran into some issues while doing some alpha testing of an addon with View → Configure options.
We quickly discovered that some key-value pair were being stored with an index. And that didn’t work well if the list being indexed is reduced. An index out of range error occurred. And the configuration management choked.
We changed the configuration setting to save a better identifier. And embedded some features to anticipate incompatible .ini files. (It saves an identifier of what module the .ini file is the target as a config_id and a schema as a config_schema version level. So if someone pastes a ‘recommended’ set of configurations into the wrong file or the schema has changed, the plugin can become aware of that. Then choose to flush it or update it.)
The thought occurs that this might be generally useful set of core features in the Configuration Management.
;; Gramps key file
;; Automatically created at 2026/01/19 00:05:01
[myopt]
bg_sel_col='#fdccff'
config_id='LocalTerm'
config_schema='0.0.1'
fg_sel_col='#613583'
lang1_file='gramps-project-glossary-en_GB.csv'
lang2_file='gramps-project-glossary-en_GB.csv'
;;search_lang=1
show_anchor=1
;;url_bas='https://gramps-project.org/wiki/index.php/'