From: H.G. Muller Date: Mon, 3 Oct 2011 07:59:40 +0000 (+0200) Subject: Update texi file for new features X-Git-Url: http://winboard.nl/cgi-bin?a=commitdiff_plain;h=ecbea6fd983169b166708a766ee596df873e758e;p=xboard.git Update texi file for new features --- diff --git a/xboard.texi b/xboard.texi index 34353e0..da12bd2 100644 --- a/xboard.texi +++ b/xboard.texi @@ -658,6 +658,7 @@ Plays a game between two chess engines. The @kbd{Ctrl-T} key is a keyboard equivalent. @item Analysis Mode @cindex Analysis Mode, Menu Item +@cindex null move XBoard tells the chess engine to start analyzing the current game/position and shows you the analysis as you move pieces around. The @kbd{Ctrl-A} key is a keyboard equivalent. @@ -675,18 +676,21 @@ clock to tell XBoard which side moves first. 4. Select Analysis Mode from the Mode Menu to start the analysis. +You can now play legal moves to create follow-up positions for the +engine to analyze, while the moves will be remembered as a stored game, +and then step backward through this game to take the moves back. +Note that you can also click on the clocks to set the opposite +side to move (adding a so-called @samp{null move} to the game). + The analysis function can also be used when observing games on an ICS with an engine loaded (zippy mode); the engine then will analyse the positions as they occur in the observed game. -@item Analyze File -@cindex Analyze File, Menu Item -This option lets you load a game from a file (PGN, XBoard format, etc.) -and analyze it. The @kbd{Ctrl-F} key is a keyboard equivalent. -When you select this menu item, a pop-up window appears -and asks for a file name to load. -If the file contains multiple games, another pop up appears that lets -you select which game you wish to analyze. -After a game is loaded, XBoard will start auto-playing the game, +@item Analyze Game +@cindex Analyze Game, Menu Item +This option subjects the currently loaded game to aoutomatic +analysis by the loaded engine. +The @kbd{Ctrl-G} key is a keyboard equivalent. +XBoard will start auto-playing the game from the currently displayed position, while the engine is analyzing the current position. The game will be annotated with the results of these analyses. In particlar, the score and depth will be added as a comment, @@ -863,9 +867,10 @@ possible arguments on the engine command line (if the engine docs say the engine needs any), and the directory where the engine should look for its files (if this cannot be deduced automatically from the specification of the engine executable). -You will also have specify (with the aid of checkboxes) if the engine is UCI. +You will also have to specify (with the aid of checkboxes) if the engine is UCI. If ‘Add this engine to the list’ is ticked (which it is by default), the engine will be added to the list of installed engines in your settings file, +(provided you save the settings!), so that next time you can select it from the drop-down list. You can also specify a ‘nickname’, under which the engine will then appear in that drop-down list, @@ -1117,6 +1122,11 @@ The flash-rate setting determines how rapidly this flashing occurs. @cindex Animation Speed, Menu Item Determines the duration (in msec) of an animation step, when @samp{Animate Moving} is swiched on. +@itemx Zoom factor in Evaluation Graph +@cindex Zoom factor in Evaluation Graph, Menu Item +Sets the valueof the @code{evalZoom} option, +indicating the factor by which the score interval (-1,1) should be +blown up on the vertical axis of the Evaluation Graph. @item Time Control @cindex Time Control, Menu Item Pops up a sub-menu where you can set the time-control parameters interactively. @@ -1318,7 +1328,7 @@ matches between two chess programs @itemx Tournament file @cindex Tournament file, Menu item To run a tournament, XBoard needs a file to record its progress, -to resume the tourney when it is interrupted. +so it can resume the tourney when it is interrupted. When you want to conduct anything more complex than a simple two-player match with the currently loaded engines, (i.e. when you select a list of participants), @@ -1366,7 +1376,7 @@ E.g. if you specified 10 engine, and tourney type = 2, the first 2 engines each play the remaining 8. A value of -1 instructs XBoard to play Swiss; for this to work an external pairing engine must be specified through the @code{pairingEngine} option. -Each Swiss round will be concidered a tourney cycle in that case. +Each Swiss round will be considered a tourney cycle in that case. Default:0 @itemx Number of tourney cycles @itemx Default number of Games @@ -1398,11 +1408,33 @@ File where the tournament games are saved These items optionally specify the file with move sequences or board positions the tourney games should start from. The corresponding numbers specify the number of the game or position in the file. -Here a value -1 means automatical stepping through all games on the file, +Here a value -1 means automatic stepping through all games on the file, -2 automatic stepping every two games. The Rewind-Index parameter causes a stepping index to reset to one after reaching a specified value. +A setting of -2 for the game number will also be effective in a tournament without +specifying a game file, but playing from the GUI book instead. +In this case the first (odd) games will randomly select from the book, +but the second (even) games will select the same moves from the book as the previous game. +(Note this leads to the same opening only if both engines use the GUI book!) Default: No game or position file will be used. The default index if such a file is used is 1. +@itemx Replace Engine +@itemx Upgrade Engine +@cindex Replace Engine, Menu Item +@cindex Upgrade Engine, Menu Item +With these two buttons you can alter the participants of an already running tournament. +After opening the Match Options dialog on an XBoard that iw playing fo the tourney, +you will see all the tourney parameters in the dialog fields. +You can then replace the name of one engine by that of another +by editing the @samp{participants} field. +(But preserve the order of the others!) +Pressing the button after that will cause the substitution. +With the @samp{Upgrade Engine} button the substitution will only affect future games. +With @samp{Replace Engine} all games the substituted engine has already played will +be invalidated, and they will be replayed with the substitute engine. +In this latter case the engine must not be playing when you do this, +but otherwise there is no need to pause the tournament play +for making a substitution. @item Load Game Options @cindex Load Game Options, Menu Item @@ -2003,10 +2035,10 @@ Indicates if the mentioned engine has its own opening book it should play from, rather than using the external book through XBoard. Default: false. @item -fn string or -firstPgnName string @itemx -sn string or -secondPgnName string -@cindex firstPgnName string, option -@cindex secondPgnName string, option -@cindex fn string, option -@cindex sn string, option +@cindex firstPgnName, option +@cindex secondPgnName, option +@cindex fn, option +@cindex sn, option Indicates the name that should be used for the engine in PGN tags of engine-engine games. Intended to allow you to install verions of the same engine with different settings, @@ -2111,6 +2143,19 @@ and “pairing N”, (where N is the number of the tourney game). To the latter the pairing engine should answer with “A-B”, where A and B are participant numbers (in the range 1-N). (There should be no reply to the results command.) Default: empty string. +@item -afterGame string +@cindex afterGame, option +When non-empty, the given string will be executed as a system command +after each tournament game. +This can be used, for example, to autmatically run a cross-table generator +on the PGN file where games are saved, to update the tourney standings. +Default: "" +@item -seedBase number +@cindex seedBase, option +Used to store the seed of the pseudo-random-number generator in the +tourneyFile, so that separate instances of XBoard working on the same +tourney can take coherent 'random' decisions, such as picking an +opening for a given game number. @end table @node ICS options @@ -2738,6 +2783,15 @@ If this option is False, xboard omits the [<<] [<] [P] [>] [>>] button bar from the window, allowing the message line to be wider. You can still get the functions of these buttons using the menus or their keyboard shortcuts. Default: true. +@item -evalZoom factor +@cindex evalZoom, option +The score interval (-1,1) is blown up on the vertical axis of +the Evaluation Graph by the given factor. +Default: 1 +@item -evalThreshold n +@cindex evalThreshold, option +Score below n (centiPawn) are plotted as 0 in the Evaluation Graph. +Default: 25 @item -mono/-xmono or -monoMode true/false @cindex mono, option @cindex monoMode, option @@ -2910,6 +2964,18 @@ On a grayscale monitor you might prefer: -premoveHighlightColor gray70 -lowTimeWarningColor gray70 @end example +@item -useBoardTexture true/false +@itemx -liteBackTextureFile filename +@itemx -darkBackTextureFile filename +@cindex useBoardTexture, option +@cindex liteBackTextureFile, option +@cindex darkBackTextureFile, option +Indicate the pixmap files to be used for drawing the board squares, +and if they should be used rather than using simple colors. +The algorithm for cutting squares out of a given bitmap is such that +the picture is perfectly reproduced when a bitmap the size of +the complete board is given. +Default: false and "" @item -drag/-xdrag or -animateDragging true/false @cindex drag, option @cindex animateDragging, option @@ -2964,6 +3030,11 @@ When true, scores on the Engine Output window during analysis will be printed from the white point-of-view, rather than the side-to-move point-of-view. Default: False. +@item -scoreWhite true|false +@cindex scoreWhite, option +When true, scores will always be printed from the white point-of-view, +rather than the side-to-move point-of-view. +Default: False. @end table @node Adjudication Options