diff options
| author | Vito Caputo <vcaputo@pengaru.com> | 2023-05-09 14:57:10 -0700 |
|---|---|---|
| committer | Vito Caputo <vcaputo@pengaru.com> | 2023-05-11 15:19:25 -0700 |
| commit | a4d52bcd363ee185ff20c74b3c97de96e314d381 (patch) | |
| tree | 0c34191ca0b31f885f733a8629ca7ab7b98a4106 /src/til.c | |
| parent | 974c464d4b2b12682d1a33a2e8ffe105bd78b519 (diff) | |
til_settings: make use of til_setting_desc_t.container
This commit pivots everything over to using desc->container as
the target settings instance when adding settings, as well as
actually assigning the settings container @ desc create.
Given nothing is actually triggering settings heirarchies yet (no
specs set as_nested_settings) this shouldn't actually result in
any realized functional difference, yet. The settings pointer
being placed in desc->container should be identical to what was
getting used before.
Diffstat (limited to 'src/til.c')
| -rw-r--r-- | src/til.c | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -337,7 +337,7 @@ int til_module_randomize_setup(const til_module_t *module, unsigned seed, til_se char *value; value = desc->spec.random(rand_r(&seed)); - til_settings_add_value(settings, desc->spec.key, value, desc); + til_settings_add_value(desc->container, desc->spec.key, value, desc); free(value); } else if (desc->spec.values) { int n; @@ -346,9 +346,9 @@ int til_module_randomize_setup(const til_module_t *module, unsigned seed, til_se n = rand_r(&seed) % n; - til_settings_add_value(settings, desc->spec.key, desc->spec.values[n], desc); + til_settings_add_value(desc->container, desc->spec.key, desc->spec.values[n], desc); } else { - til_settings_add_value(settings, desc->spec.key, desc->spec.preferred, desc); + til_settings_add_value(desc->container, desc->spec.key, desc->spec.preferred, desc); } } |