Re: [Bug-gnubg] unwanted extension of rollouts

[Jim Segrave]

On Mon 04 Aug 2003 (07:52 +0000), Joern Thyssen wrote:
> On Mon, Aug 04, 2003 at 09:14:09AM +0200, Jim Segrave wrote
> 
> > Maybe the best solution is a pop-up dialogue box that warns you that a
> > move you have selected for rolling out was rolled out with different
> > settings than the current ones with options to 
> 
> You need to add a new callback function to the rollout subroutines,
> since there is no GTK+ code in the rollout code. Also, this extends to
> the command line interface. 

True. 
But this sort of thing, if it should be done at all, ought to happen
either from the gtkcube.c/gtkchequer.c widgets or from CommandRollout
in gnubg.c, since the way around this is to 

warn the user
switch {
  forget it:
    whatever routine it is simply returns
  
  extend with old settings:
    carry on with the call as per the old code

  redo it with the new settings:
    presumably here you actually know where to find the move records,
    so you can set the analyis type to EVAL_NONE, then carry on with
    the old code as RolloutGeneral() will automatically use the current
    rollout settings if the eval setup isn't already marked as a
    rollout.

The number of places to change is fairly small if people think this is
something to implement.

I'm ambivalent - if you see it's resuming a rollout and you don't want
it to, you just hit stop, 0 ply eval, then rollout. I think it's more
of a pain having to know exactly what the settings were to ensure that
you can extend a rollout - one mistake and your data is gone.

-- 
Jim Segrave           address@hidden