From 980880be1f2801b2a69fcc67abc0f5827fd106f2 Mon Sep 17 00:00:00 2001 From: Simon Tatham Date: Sat, 2 Apr 2011 16:19:12 +0000 Subject: Add a function to every game backend which indicates whether a game state is in a solved position, and a midend function wrapping it. (Or, at least, a situation in which further play is pointless. The point is, given that game state, would it be a good idea for a front end that does that sort of thing to proactively provide the option to start a fresh game?) [originally from svn r9140] --- midend.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) (limited to 'midend.c') diff --git a/midend.c b/midend.c index 300e2bf..0c8b3c0 100644 --- a/midend.c +++ b/midend.c @@ -1336,6 +1336,21 @@ char *midend_solve(midend *me) return NULL; } +int midend_is_solved(midend *me) +{ + /* + * We should probably never be called when the state stack has no + * states on it at all - ideally, midends should never be left in + * that state for long enough to get put down and forgotten about. + * But if we are, I think we return _true_ - pedantically speaking + * a midend in that state is 'vacuously solved', and more + * practically, a user whose midend has been left in that state + * probably _does_ want the 'new game' option to be prominent. + */ + return (me->statepos == 0 || + me->ourgame->is_solved(me->states[me->statepos-1].state)); +} + char *midend_rewrite_statusbar(midend *me, char *text) { /* -- cgit v1.1