[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] Re: Final GTK 1.3 Build, gnubg Documentation Bug Report

From: Jim Curtis
Subject: Re: [Bug-gnubg] Re: Final GTK 1.3 Build, gnubg Documentation Bug Report
Date: Wed, 27 Apr 2005 16:25:15 -0700

Thanks for the help with adjusting the settings!

Regarding the evaluations I used the default analysis (world class) settings of the final 1.3 build for each match that gnubg analyzed. Perhaps someone else has noticed this? Or maybe I'm missing something. I'll take another look.

I would suggest "<playername> will not use 'pruning' neural net" for System default, English, etc. as opposed to 'prunning' which is not used in any English dictionaries I have seen.

Again, many thanks for this awesome program!

Jim Curtis

----- Original Message ----- From: "Øystein O Johansen" <address@hidden>
To: <address@hidden>
Cc: "Bug-gnubg" <address@hidden>
Sent: Wednesday, April 27, 2005 3:16 AM
Subject: Re: [Bug-gnubg] Re: Final GTK 1.3 Build, gnubg Documentation Bug Report

First of all, major thanks to everyone involved in writing
this program and in continuing its development.  Really
great software!

From all of us involved: Thank you!

1.  After analyzing a match, I've noticed that some, not all, of
the moves shown in "details" as being doubtful, bad, etc. are not
marked as such with the color scheme in the "move record" window.
I've observed this in analysis of multiple matchs.

Hmmm... I have not seen this my self. Are the evaluations with the
same settings?

2.  There is a typographical and grammatical error: "gnubg don't
use prunning", for example, in neural net dialog box.

I guess "<playername> will not use prunning neural net" is better?

3.  Although I think the same nice font is being used for all the
menus, dialog boxes and analysis I find it is now smaller, and I
think the larger size is better suited for studying the analysis
and the program's appearence in general.

you can set a different font size (or font type) in your gnubg.gtkrc
file. Open the file in a text editor and change find a line that says
something like:

font = "-unknown-tahoma-normal-r-normal-*-*-90-*-*-p-*-iso8859-1"

Change the 90 to say 120. That's the number controlling the font
size. You can also change the font type. Line is the file that
starts with # are comments. When you do a change to this file, you
have to save it and restart gnubg.

4.  The musical fanfare at opening and organ riff at closing
the program are now missing, much to my chagrin. I think they're
very cool and would at least like the option of playing them.

You can type in the command field:

set sound sound start "fanfare.wav"

for setting the closing sound you type:

set sound sound exit "haere-ra.wav"

We don't have any graphic suer interface for setting the sounds.

5.  My last concern has to do with gnubg.org.  First, it looks
great and is well thought out.  My concern regards the
Documentation Wiki pages where there appears to be an error in
rendering the images.  When loading the "gnubg manual" pages the
images would not load, leaving the text "embedded image" where the
picture should be.

It's a problem with the webserver. The web server is hosted by a
german company and offer this for free. When I set up the wiki things
worked fine (running DokuWiki) the images whas there. Then the they
decided to run PHP in CGI mode and then the images wasn't visible any
more. I know the reason why, but I can't do any thing about it. We're
just having the web space and domain name. I can't configure the web

We have mail them, but they are not very responsive.

I either have to wait and hope that they won't run PHP in CGI mode
after the next upgrade. Or I can disable the possibility to upload
images. Or I can work out another solution.

In closing, thanks again for the program and the opportunity to
offer input.

Thanks for your feedback!


The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]