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).
Other things : when one or more "sub-windows"
are open (e.g. hint), they don't appear
as "independent windows" (they
don't have their icon in the taskbar) and this causes some
strange bahaviors like :
- gnubg win + hint win (1 icon in the
- reduce all windows (right-click on
the taskbar, 'Minimize all windows')
- click on the gnubg icon in the taskbar
and only the hint window is restored
Also, the rollout proress window has
a srange behavior :if iconized, the icon doesn't go to
the taskbar (but stays on the desktop).