Jonathan Kinsey <address@hidden> wrote
on 17/07/2009 16:47:08:
> Max, I'm not sure how you can accidentally click on the board often
> computer is thinking)?
> In general a user might not be sure what is happening and clicking
> the board and
> nothing happening isn't the best answer. Maybe the message could be
> improved to
> something like, "The computer is thinking, interrupt the current
I would say that most of the time is when gnubg is
moving (chequers are moving) and I click too early. Not a big deal but
since interrupting could lead to strange situations (you have to force
gnubg to play his roll) it looks kinda messy for a non-expert user.
I wouldn't expect gnubg to react while he's thinking/moving,
except to the stop button. The spinning hourglass indicates
gnubg is thinking (btw, there's no hourglass while chequers are being
moved around by gnubg), even a naive user knows gnubg is working.
My point is only that, as it is today, it is way too
easy to stop gnubg compared to the number of cases where yuo really need
to do it (close to never ?). Stop button is fine: it's small and almost
hidden. If you need to stop gnubg, you're smart enough to loko around
for the button.
I have no idea when this feature came in, but I'm
positive that it wasn't there in the past.