aboutsummaryrefslogtreecommitdiff
path: root/midend.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2023-04-21 15:50:05 +0100
committerSimon Tatham <anakin@pobox.com>2023-04-23 13:25:06 +0100
commit0058331aeb027f7441a04d99cc7c1e445bd896d9 (patch)
treedbc122795b93195c7bb1b7c7b51e50927b547415 /midend.c
parent0d1a1f08bac25a4641c38a8e42dfa6e2bb9981d7 (diff)
downloadpuzzles-0058331aeb027f7441a04d99cc7c1e445bd896d9.zip
puzzles-0058331aeb027f7441a04d99cc7c1e445bd896d9.tar.gz
puzzles-0058331aeb027f7441a04d99cc7c1e445bd896d9.tar.bz2
puzzles-0058331aeb027f7441a04d99cc7c1e445bd896d9.tar.xz
New backend functions: get_prefs and set_prefs.
These are similar to the existing pair configure() and custom_params() in that get_prefs() returns an array of config_item describing a set of dialog-box controls to present to the user, and set_prefs() receives the same array with answers filled in and implements the answers. But where configure() and custom_params() operate on a game_params structure, the new pair operate on a game_ui, and are intended to permit GUI configuration of all the settings I just moved into that structure. However, nothing actually _calls_ these routines yet. All I've done in this commit is to add them to 'struct game' and implement them for the functions that need them. Also, config_item has new fields, permitting each config option to define a machine-readable identifying keyword as well as the user-facing description. For options of type C_CHOICES, each choice also has a keyword. These keyword fields are only defined at all by the new get_prefs() function - they're left uninitialised in existing uses of the dialog system. The idea is to use them when writing out the user's preferences into a configuration file on disk, although I haven't actually done any of that work in this commit.
Diffstat (limited to 'midend.c')
0 files changed, 0 insertions, 0 deletions