Re: [Bug-gnubg] Problem using command files for rollouts.

[Holger]

At 00:12 25.02.2003 +0100, Jim Segrave wrote:
> On Mon 24 Feb 2003 (13:07 -0000), Ian Shaw wrote:
> > If I set up a command file to do several rollouts, it works up to the 
> point when the first rollout is complete. GnuBg then sits there waiting 
> for me to press OK before continuing on to the next rollout.
> > I can't find any settings to turn this feature off, which precludes me 
> from running untended rollouts.
> > I've got
> > set message on
> > set confirm new off
> > set confirm save off
> >
> > Is there any way round this, or could there be one? I'd use 
> gnubg_no_gui, but there isn't an up to date build.
>
> I was looking at the code and had the following thought, but I'm no
> expert in gtk windows etc.
>
> If we had a global that was set in gnubg.c:LoadCommands() to indicate
> it was running a command file, then maybe the rollout command could
> issue a "clicked" signal to the OK button for the Rollout window (of
> course that part of the code would go in gtkgame.c, not rollout.c, but
> rollout.c could call a function to conditionally clear the window if
> we're running a command file.
>
> Do any gtk experts know if this is the right way to achieve this?

I'm no expert, but will give my 2ct:
I suppose it might help if outputresume() isn't called until the global 
flag isn't cleared. So if there are queued tasks and no errors no output is 
given, and only at the end of LoadCommands() outputresume() gets called. 
Maybe then the global could even be omitted.
If the queued text might get too much, one could also think about writing 
all into a file.

Regards,

        Holger