From: H.G. Muller <h.g.muller@hccnet.nl>
Date: Sun, 7 Oct 2012 19:00:10 +0000 (+0200)
Subject: Use Pause state in AnalyzeMode to imply move exclusion
X-Git-Url: http://winboard.nl/cgi-bin?a=commitdiff_plain;h=0a568b08637f0de830db645352ea96b6a1bcf866;p=xboard.git

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.
---

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;