Since the clock doesn't start until after White's first move, it
shouldn't be possible to pause/unpause the game during this time,
either. This means the pause button must be insensitive, and we don't
want to see any warnings if we unfocus the window prior to making the
first move.
Stock icons have also been deprecated by Gtk+, but aren't yet marked so
by Vala. Let's leave these be for now, as I'm not sure how to handle
icon sensitivity.
This went unnoticed because they were used reversed, due to the
confusing parameter name in GnomeChess.set_paused_state.
The previous commit was more prescient than I'd hoped....
This isn't really a fix, as every engine that limits depth to 2
(including Glaurung) will just search to 2 if told to use depth 1. But
it's nice to keep the config file consistent with reality.
You can now specify arguments to UCI "go" in engines.conf. An example
command would be "go depth 1" or "go nodes 20" (to expand only 20 nodes
per level), or in combination "go depth 1 nodes 20". See the UCI spec
for a full list of valid commands.
* Instead of public fields, use properties with private setters.
* Change associated free functions into static class functions
* Warn on error reading KeyFile
I'm really excited about how easy HoiChess is to beat. It must not be
using any extensions/quiescence at all. However this does make it
extremely unrealistic to play against at depth 1.
I was disappointed when I discovered that most engines did not respect
the depth command. But it turns out that this is a GNUChess (and
Phalanx)-specific extension. Everyone else uses sd for the same
purpose. This means that we get to provide meaningful difficulties for
these engines after all. Yay!
Blitz Chess is typically five minutes per player (10 minutes total). If
you want to go faster than that, you can always set a custom duration.
Most players will probably be most comfortable with a longer limit such
as 90 minutes/player.
This isn't a board orientation, it's a piece orientation. It actually
silently forces the "White" board orientation.
It could be implemented separately as a checkbox, but I don't think we
want to keep this "feature."
Also, this option is broken in 3D mode. (Though as a checkbox, it could
be insensitive in 3D mode.)
