Closed GoogleCodeExporter closed 9 years ago
You are right.
However the thing is, that engines identify themselves as "id name Fruit 2.1" or
myname="GNU Chess 5.07". There isn't any real way to figure out what is the
number
and what is the engine.
One solution would be to test if the last "word" in a name consisted only of
numbers
and fullstops. It never would be perfectly secure though.
Perhaps a better solution would be simple to cut the string name in the end,
rather
than in the middle, as we currently do.
Original comment by lobais
on 2 Nov 2007 at 5:37
I like to see the names with versions in it, but it's only my taste of course.
Original comment by gbtami
on 2 Nov 2007 at 7:53
Hm, simply changing ELLIPSIZE_MIDDLE to ELLIPSIZE_END probably isn't a good idea
after all.
When you see version numbers for all engines but one, you get currious what it
is.
Then it's much easier to guess the middle name.
Eventually we'll probably have to wait for the "install" engine dialog to be
implemented (already mocked up in glade in the preferences.glade file). It
should
have a field to manually set the name.
Original comment by lobais
on 16 Nov 2007 at 6:18
As pychess only works with known chess engines, can't the displayed chess
engine name
just be added to its properties in engines.xml?
Original comment by wouterst...@gmail.com
on 30 Dec 2007 at 10:38
I don't think hiding the version is a good idea generally - think of Rybka 2
and Rybka 4, those are a huge different deal and it should be possible to tell
them apart. The minor version might be less important, but the major version
certainly is.
Also the .PGN files exported should really ALWAYS have the engine version in
them, or they'll lose an important piece of information when archived.
And I might be unusual in regards of this, but I regularly have many engine
versions around which I like to tell apart.
Original comment by jonas.thiem@gmail.com
on 30 Aug 2012 at 7:28
With new engine dialog in 0.12beta1 it's possible to edit engine names.
Original comment by gbtami
on 27 Mar 2013 at 7:55
Original issue reported on code.google.com by
wouterst...@gmail.com
on 2 Nov 2007 at 4:30