From 73daff393722196bf48244ca95dd4f64a351a473 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sun, 19 Jun 2011 13:43:35 +0000 Subject: Changed my mind about midend_is_solved: I've now reprototyped it as midend_status(), and given it three return codes for win, (permanent) loss and game-still-in-play. Depending on what the front end wants to use it for, it may find any or all of these three states worth distinguishing from each other. (I suppose a further enhancement might be to add _non_-permanent loss as a fourth distinct status, to describe situations in which you can't play further without pressing Undo but doing so is not completely pointless. That might reasonably include dead-end situations in Same Game and Pegs, and blown-self-up situations in Mines and Inertia. However, I haven't done this at present.) [originally from svn r9179] --- range.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'range.c') diff --git a/range.c b/range.c index 6bdba76..afb2de6 100644 --- a/range.c +++ b/range.c @@ -1485,9 +1485,9 @@ static float game_flash_length(game_state *from, game_state *to, return 0.0F; } -static int game_is_solved(game_state *state) +static int game_status(game_state *state) { - return state->was_solved; + return state->was_solved ? +1 : 0; } /* ---------------------------------------------------------------------- @@ -1737,7 +1737,7 @@ struct game const thegame = { game_redraw, game_anim_length, game_flash_length, - game_is_solved, + game_status, TRUE, FALSE, game_print_size, game_print, FALSE, /* wants_statusbar */ FALSE, game_timing_state, -- cgit v1.1