Re: [Bug-gnubg] Advance to error buttons

[Jim Segrave]

On Tue 10 Sep 2002 (11:32 +0100), Ian Shaw wrote:
> The advance  to error buttons on the annotation window could function
> better.
> 
> At present the jump take you to the cube decision display, before the dice
> roll.
> 
> If it is a chequer play problem it would be better to display the position
> with the dice rolled.
> 
> At the moment I find it takes a while to work out exactly what I am looking
> at.

You get the same thing with the next move button, so I tried to make
it consistent there. On the previous move button, you go to the dice
rolled position, whereas previous marked takes you to the cube
decision position. Maybe this should change, but I had some problems
getting this to work right, because you need to consider if you are
currently on a marked move.
 
> An extra nice feature would be a drop down selector to allow the user to
> skip to doubtful/bad/very bad.

There's not a lot of room for a dropdown menu on the Game Record
window. It would have to be on a new line above/below the buttons. But
if there were such a setting, the change to skip some levels of error
would be trivial. At the moment, there's a routine MoveIsMarked which
simply checks if the Chequer or Cube play has a skill rating that's
not SKILL_NONE (i.e. not worth commenting about).

> Since we've been talking about terminology, how about using "error" and
> "blunder" instead of "bad", "very bad"? These terms seem to be in fairly
> common use.
> 
> When the Good Moves feature is implemented, will we be able to include these
> in the navigation?

At the moment that would happen automatically, as they wouldn't have
SKILL_NONE. If we had a menu to set thresholds, then we'd have to take
these into account (there's an ordering from

SKILL_VERYBAD..SKILL_NONE..SKILL_VERYGOOD, so it's easy to dpo this
sort of thing.

The patches I sent in to allow re-analysing all marked moves still
apply as of the current source. I'm not convinced it's terribly useful
(at first I thought it was, but lately I've not used it often).

-- 
Jim Segrave           address@hidden