Christian Anthon <address@hidden>
wrote on 13/07/2009 17:48:43:
> On Mon, Jul 13, 2009 at 3:17 PM, Massimiliano
> Maini<address@hidden> wrote:
> >
> > Hi,
> >
> > I just realized that clicking on the board while gnubg is thinkingon
a move
> > now pops up a dialog "Interrupt the current process ? OK/No".
> > Not sure it has always been like this. Anyway, proabbly not a
good idea.
> >
>
> Debatable I guess. What action would you like gnubg to take in this
> case? Personally I find it very frustrating when you interact with
a
> busy program that replies by doing nothing in return (or beeps).
Debatable indeed. Maybe it was just me being unaccustomed
to it, but it happened a lot to click by mistake and get the dialog,
very annoying.
The fact gnubg is "alive" is shown by the
spinning hourglass. In case you really want to stop gnubg thinking, there's
the stop button. I suspect this action (stop gnubg) is used on rare
occasions. Hence I would prefer no action for any click when
gnubg is thinking, except for clicks on the stop button.