> Massimiliano Maini wrote:
> >
> > Hi all,
> >
> > I noticed some funky behaviour of gnubg (0.16) under Windows
(at least
> > on 2000 at office, will check XP at home).
> >
> > If I minimize the gnubg window to the takbar and then I right-click
on
> > its icon on the taskbar
> > and click on "Close", then gnubg is stuck for a while
: it doesn't
> > disappear and the icon on the
> > taskbar is "frozen" (impossible to restore the window,
no context menu,
> > etc).
> >
> > This makes me think also to a user that posted to rgb that using
the
> > command line version
> > in a batch script (to do rollouts) was very slow, and the reason
was
> > that the script had to
> > wait a long time for gnubg to process the "exit" command
... (I don't
> > have any detail on this
> > problem, II've asked him to post to the mailing list).
>
> Are sounds on? If so the pause is waiting for the exit sound
to
> play (finish).
Maybe the origin of the problem is that if you quit
gnubg within an ongoing match/session, it raises a popup asking for
confirmation.
If I run gnubg and as soon as it appears I minimiwe
its window and then right-cilck on the takbar icon and "Close",
it disappears immediately. But if I run gnubg, start a match, minimize the windows,
and then right-cilck on the takbar icon and "Close",
then it doesn't disappear. I get the context menu, and the "Restore"
thing works, but the gnubg window is then frozen, with no way to quit (except
task manager terminate).
[BTW, I have sound switched off and no 3d-board closing,
but the sound thing could be the origin of the command-line case
reported on rgb]
> I've wondered several times why the hint dialog isn't modal (i.e.
> you can leave
> it open and do other things), I don't think it updates if you make
a move.
> Anyone know why? If not, changing it to a modal window would
fix (hide) this.
I think it should be modal.
> > Also, the rollout proress window has a srange behavior :if iconized,
the
> > icon doesn't go to
> > the taskbar (but stays on the desktop).
>
> This is what happens to dialogs (that haven't got a taskbar window)
when they
> are minimised. We can either make the rollout window have a
taskbarwindow all
> the time or (possibly) when it's minimised - or live with it as it
is...
Just like the hint window, I think the rollout one
should be modal : is there anything you should be able to do in the main window
while a rollout is ongoing ? And while a hint is ongoing ? Don't think so, maybe just quitting and stopping,
but rollouts can be stopped with their own stop button, hints should have their
own stop button too (in case somebody fances a 4ply hint or runs a 3ply
on a 386).