-@item Time Control
-@cindex Time Control, Menu Item
-Pops up a sub-menu where you can set the time-control parameters interactively.
-Allows you to select classical or incremental time controls,
-set the moves per session, session duration, and time increment.
-Also allows specification of time-odds factors for one or both engines.
-If an engine is given a time-odds factor N, all time quota it gets,
-be it at the beginning of a session or through the time increment or
-fixed time per move, will be divided by N.
-The shifted @kbd{Alt+T} key is a keyboard equivalent.
-@item Common Engine
-@cindex Common Engine, Menu Item
-Pops up a sub-menu where you can set some engine parameters common to most engines,
-such as hash-table size, tablebase cache size, maximum number of processors
-that SMP engines can use, and where to find the Polyglot adapter needed
-to run UCI engines under XBoard. The feature that allows setting of these parameters on
-engines is new since XBoard 4.3.15, so not many XBoard/WinBoard engines respond
-to it yet, but UCI engines should.
-
-It is also possible to specify a GUI opening book here, i.e. an opening
-book that XBoard consults for any position a playing engine gets in.
-It then forces the engine to play the book move, rather than to think up its own,
-if that position is found in the book.
-The book can switched on and off independently for either engine.
-The way book moves are chosen can be influenced through the settings of
-book depth and variety.
-After both sides have played more moves than the specified depth,
-the book will no longer be consulted.
-When the variety is set to 50, moves will be played with the probability
-specified in the book.
-When set to 0, only the move(s) with the highest probability will be played.
-When set to 100, all listed moves will be played with equal pobability.
-Other settings interpolate between that.
-The shifted @kbd{Alt+U} key is a keyboard equivalent.
-@item Adjudications
-@cindex Adjudications, Menu Item
-Pops up a sub-menu where you can enable or disable various adjudications
-that XBoard can perform in engine-engine games.
-The shifted @kbd{Alt+J} key is a keyboard equivalent.
-You can instruct XBoard to detect and terminate the game on checkmate
-or stalemate, even if the engines would not do so, to verify engine
-result claims (forfeiting engines that make false claims), rather than
-naively following the engine, to declare draw on positions
-which can never be won for lack of mating material, (e.g. KBK),
-or which are impossible to win unless the opponent seeks its own demise
-(e.g. KBKN).
-For these adjudications to work, @samp{Test Legality} should be switched on.
-It is also possible to instruct XBoard to enforce a 50-move or 3-fold-repeat
-rule and automatically declare draw (after a user-adjustable number of moves
-or repeats) even if the engines are prepared to go on.
-It is also possible to have XBoard declare draw on games that seem to drag on
-forever, or adjudicate a loss if both engines agree (for 3 consecutive moves) that one
-of them is behind more than a user-adjustable score threshold.
-For the latter adjudication to work, XBoard should be able to properly understand
-the engine's scores. To facilitate the latter, you can inform xboard here if
-the engines report scores from the viewpoint of white, or from that of their own color.
-@item Match Game Options
-@cindex Match Game Options, Menu Item
-Summons a dialog where you can set options important for playing automatic
-matches between two chess programs
-(e.g. by using the @samp{Machine Match} menu item in the @samp{Mode} menu).
-You can specify the number of games such a match should last,
-and the duration of the pause between games
-(important for some older engines to not have the last move of a previous
-game be given when the next game has already started).
-You can also specify a file with opening lines, or a file with initial positions
-(the @code{loadGameFile} and @code{loadPositionFile} options),
-and the number of the game or position to use from these files.
-Values -1 and -2 of this 'index' convey a special meaning,
-namely that XBoard should automatically step through all lines or positions
-in these files.
-With -1 such stepping is done every game; with -2 every two games,
-so that each line or position is played with both colors before stepping
-to the next one.
-You can have XBoard automatically rewind to the first line or position
-in the file after the index reaches a certain vaue,
-which you can also specify here.
-
-
-@item Match
-@cindex Match, Menu Item
-@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.
-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),
-you must not leave this field blank.
-When you enter the name of an existing tournament file,
-XBoard will ignore all other input specified in the dialog,
-and will take them from that tournament file.
-This resumes an interrupted tournament, or adds another XBoard
-agent playing games for it to those that are already doing so.
-Specifying a not-yet-existing file will cause XBoard to create it,
-according to the tournament parameters specified in the rest of the dialog,
-before it starts the tournament on ‘OK’.
-Provided that you specify participants;
-without participants no tournament file will be made, but other entered values
-(e.g. for the file with opening positions) will take effect.
-Default: configured by the @code{defaultTourneyName} option.
-@itemx Sync after round
-@itemx Sync after cycle
-@cindex Sync after round, Menu Item
-@cindex Sync after cycle, Menu Item
-The sync options, when on, will cause WinBoard to refrain from starting games
-of the next round or cycle before all games of the previous round or cycle are finished.
-This guarantees correct ordering in the games file,
-even when multiple XBoard instances are concurrently playing games for the same tourney.
-Default: sync after cycle, but not after round.
-@itemx Select Engine
-@itemx Tourney participants
-@cindex Select Engine, Menu Item
-@cindex Tourney participants, Menu Item
-With the Select Engine combobox you can pick an engine from your list
-of installed engines in the settings file, to be added to the tournament.
-The engines selected so far will be listed in the ‘Tourney participants’ memo.
-The latter is a normal text edit, so you can use normal text-editing functions
-to delete engines you selected by accident, or change their order.
-Do not type names yourself there, because names that do not exactly match
-one of the names from the combobox will lead to undefined behavior.
-@itemx Tourney type
-@cindex Tourney type, Menu Item
-Here you can specify the type of tournament you want.
-XBoard’s intrinsic tournament manager support round-robins (type = 0),
-where each participant plays every other participant, and (multi-)gauntlets,
-where one (or a few) so-called ‘gauntlet engines’ play an independent set of opponents.
-In the latter case, you specify the number of gauntlet engines.
-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.
-Default:0
-@itemx Number of tourney cycles
-@itemx Default number of Games
-@cindex Number of tourney cycles, Menu Item
-@cindex Default number of Games, Menu Item
-You can specify tourneys where every two opponents play each other multiple times.
-Such multiple games can be played in a row,
-as specified by the ‘number of games per pairing’,
-or by repeating the entire tournament schedule a number of times
-(specified by the ‘number of tourney cycles’).
-The total number of times two engine meet will be the product of these two.
-Default is 1 cycle;
-the number of games per pairing is the same as the default number of match games,
-stored in your settings file through the @code{defaultMatchGames} option.
-@itemx Save Tourney Games
-@cindex Save Tourney Games, Menu Item
-File where the tournament games are saved
-(duplicate of the item in the @samp{Save Game Options}).
-@itemx Game File with Opening Lines
-@itemx File with Start Positions
-@itemx Game Number
-@itemx Position Number
-@itemx Rewind Index after
-@cindex Game File with Opening Lines, Menu Item
-@cindex File with Start Positions, Menu Item
-@itemx Game Number, Menu Item
-@itemx Position Number, Menu Item
-@itemx Rewind Index after, Menu Item
-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,
--2 automatic stepping every two games.
-The Rewind-Index parameter causes a stepping index to reset to one after reaching
-a specified value.
-Default: No game or position file will be used. The default index if such a file is used is 1.
-
-@item Load Game Options
-@cindex Load Game Options, Menu Item
-Summons a dialog where you can set the @code{autoDisplayComment} and
-@code{autoDisplayTags} options, (which control popups when viewing loaded games),
-and specify the rate at which loaded games are auto-played,
-in seconds per move (which can be a fractional number, like 1.6).
-@item Save Game Options
-@cindex ave Game Options, Menu Item
-Summons a dialog where you can specify the files on which XBoard should
-automtically save any played or entered games,
-(the @code{saveGameFile} option),
-or the final position of such games (the @code{savePositionfile} option).
-You can also select 'auto-save' without a file name,
-in which case XBoard will prompt the user for a file name after each game.
-You can also set the default value for the PGN Event tag that will
-be used for each new game you start.
-Various options for the format of the game can be specified as well,
-such as whether scores and depths of engine games should be saved as comments,
-and if a tag with info about the score with which the engine came out of book
-should be included.
-For Chess, always set the format to PGN, rather than "old save stye"!
-@item Game List
-@cindex Game List Tags, Menu Item
-Pops up a dialog where you can select the PGN tags that should appear
-on the lines in the game list, and their order.
-@item Sound Options
-@cindex Sound Options, Menu Item
-Summons a dialog where you can specify the sounds that should accompany
-various events that can occur XBoard.
-Most events are only relevant to ICS play,
-but the move sound is an important exception.
-For each event listed in the dialog,
-you can select a standard sound from a menu.
-You can also select a user-supplied sound file,
-by typing its name into the designated text-edit field first,
-and then selecting "Above WAV File" from the menu for the event.
-A dummy event has been provided for trying out the sounds with the
-"play" button next to it.
-The directory with standard sounds, and the external program for playing
-the sounds can be specified too, but normally you would not touch these
-once XBoard is properly installed.
-@itemx Move Sound
-@cindex Move Sound, Menu Item
-When a move sound other than 'None' is selected,
-XBoard alerts you by playing a sound
-after each of your opponent's moves (or after every
-move if you are observing a game on the Internet Chess Server).
-The sound is not played after moves you make or moves read from a
-saved game file.
-If you turn on this option when using XBoard with the Internet
-Chess Server, you will probably want to give the
-@kbd{set bell 0}
-command to the ICS, since otherwise the ICS will ring the terminal bell
-after every move (not just yours). (The @file{.icsrc} file
-is a good place for this; see @ref{ICS options}.)