aboutsummaryrefslogtreecommitdiff
path: root/loopgen.c
diff options
context:
space:
mode:
authorSimon Tatham <anakin@pobox.com>2011-09-18 07:43:19 +0000
committerSimon Tatham <anakin@pobox.com>2011-09-18 07:43:19 +0000
commit3107237af4aa82f538826e989ee7633e0a1ba22c (patch)
tree32968c9b708e47c1ee3ec781faa032801e1ee808 /loopgen.c
parent295fb9fd83512432404cd701c8b09bae4e627e20 (diff)
downloadpuzzles-3107237af4aa82f538826e989ee7633e0a1ba22c.zip
puzzles-3107237af4aa82f538826e989ee7633e0a1ba22c.tar.gz
puzzles-3107237af4aa82f538826e989ee7633e0a1ba22c.tar.bz2
puzzles-3107237af4aa82f538826e989ee7633e0a1ba22c.tar.xz
Remove the 'cheated' flag in Range's game_ui, which was stickily
remembering whether the player had ever used the hint or solve functions, even if they then pressed undo (and even if they saved and restored). As far as Solve+Undo is concerned, this just brings Range into line with common practice in the rest of my puzzles. On the other hand, Range is the first time there's been a 'hint' function to consider in this question, so here's a policy decision: the victory flash is not a congratulation for a puzzle solved unaided, it's a confirmation that you really have reached a correct solution and haven't made any mistakes. So the only reason to omit the victory flash is if you've used the Solve operation to go straight to a guaranteed-correct solution _in a single move_; if you're using the hint button, there's still scope for you to make mistakes in all your non-hint moves, so the victory flash is still a useful indicator that you didn't. [originally from svn r9306]
Diffstat (limited to 'loopgen.c')
0 files changed, 0 insertions, 0 deletions