From 0a568b08637f0de830db645352ea96b6a1bcf866 Mon Sep 17 00:00:00 2001 From: H.G. Muller Date: Sun, 7 Oct 2012 21:00:10 +0200 Subject: [PATCH 1/1] Use Pause state in AnalyzeMode to imply move exclusion The pause state was not used in AnalyzeMode so far. Now it is used to imply all entered moves are for exclusion/inclusion. --- backend.c | 4 ++++ 1 files changed, 4 insertions(+), 0 deletions(-) diff --git a/backend.c b/backend.c index 6977595..564b95e 100644 --- a/backend.c +++ b/backend.c @@ -7102,6 +7102,9 @@ LeftClick (ClickType clickType, int xPix, int yPix) return; } doubleClick = FALSE; + if(gameMode == AnalyzeMode && pausing && first.excludeMoves) { // use pause state to exclude moves + doubleClick = TRUE; gatingPiece = boards[currentMove][y][x]; + } fromX = x; fromY = y; toX = toY = -1; if(!appData.oneClick || !OnlyMove(&x, &y, FALSE) || // even if only move, we treat as normal when this would trigger a promotion popup, to allow sweep selection @@ -13379,6 +13382,7 @@ PauseEvent () WhiteOnMove(forwardMostMove))) { StopClocks(); } + case AnalyzeMode: pausing = TRUE; ModeHighlight(); break; -- 1.7.0.4