Re: [Bug-gnubg] more on movefilters

[Øystein O Johansen]

> Hi all,

Hi Jørn!

> I like the new movefilters, however, I think we should
> have one set of movefilters for hint and another set
> for analysis (and possibly a third set for gnubg's play).

Sure, I also like the movefilters. It's so much more
general.

> For example, I might play against gnubg with a rather
> small search space, but analyse the match with a larger
> search space. It's a bit annoying having to change back
> and forth.

Sure.

> We may even generalise this to having a set of
> movefilters for each
>
> "set .... chequerplay" command.

Isn't it quit easy to add a movfilter to each EvalContext?
movefilter as a member of the struct? The command will then
be:

set eval chequerplay evaluate movefilter 1 0 0 0
set analysis chequerplay evaluate movefilter 1 0 0 0

> I'll implement a GTK widget for setting up movefilters.
> At first, there will just be a number of predefined
> settings, but eventually the user may select her own.

I suggest a widget on it's own, which can be opened from the
EvalWidget with a small button. (The EvalWidget function
can then take a bolean argument if the
"Set move filter..."  button should be active or not. The
set movefilter button should not be active if it is a cube
decision.)

> Any comments on this -- or someone else volunteering to
> implement this :-)

> Jørn

-Øystein
(You have probably thought of all of this already!)


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.