ref: 493d2fb138ba64faf795e1b4c01fd4f0d49075fc
parent: 8d81c1814d249d3aa2342c02363a0220c54bf71c
author: Ben Harris <bjh21@bjh21.me.uk>
date: Mon Dec 5 07:49:51 EST 2022
Devel docs: make it clear that decode_ui() gets a new game_ui At least one puzzle does no actual decoding in decode_ui, but does re-initialise some fields. This is unnecessary because the mid-end only calls decode_ui() with a game_ui it just allocated using new_ui().
--- a/devel.but
+++ b/devel.but
@@ -890,8 +890,8 @@
\c void (*decode_ui)(game_ui *ui, const char *encoding);
This function parses a string previously output by \cw{encode_ui()},
-and writes the decoded data back into the provided \c{game_ui}
-structure.
+and writes the decoded data back into the freshly-created \c{game_ui}
+structure provided.
\S{backend-changed-state} \cw{changed_state()}