> > It no longer crashes on my side but I don't see any message. Don't
know
> > where the outputf ends up ...
> >
>
> It is discarded during startup, but end's in the message bar in the
> bottom or in a message window depending on the length of the string.
OK, got it. In facts (at least for me)
On 5/30/07, Massimiliano Maini <[EMAIL PROTECTED]> wrote:
> Locating the files should be correct now, and I've made missing files
> produce a message instead of an error.
It no longer crashes on my side but I don't see any message. Don't know
where the outputf ends up ...
It is discarded
> Locating the files should be correct now, and I've made missing files
> produce a message instead of an error.
It no longer crashes on my side but I don't see any message. Don't know
where the outputf ends up ...
MaX.
___
Bug-gnubg mailing list
Bug-gn
Locating the files should be correct now, and I've made missing files
produce a message instead of an error.
Christian.
On 5/30/07, Achim Mueller <[EMAIL PROTECTED]> wrote:
* Massimiliano Maini <[EMAIL PROTECTED]> [070530 13:35]:
> Hi all,
> latest code, sound enabled (fanfare.wav played at ope
* Massimiliano Maini <[EMAIL PROTECTED]> [070530 13:35]:
> Hi all,
> latest code, sound enabled (fanfare.wav played at opening).
>
> if the target file is missing, en error dialog appears at startup but
> closing it makes gnubg crash.
I also experienced some errors with the latest development v
Hi all,
latest code, sound enabled (fanfare.wav played at opening).
if the target file is missing, en error dialog appears at startup but
closing it makes gnubg crash.
MaX.
___
Bug-gnubg mailing list
Bug-gnubg@gnu.org
http://lists.gnu.org/mailman/list
