Since only a few of you are familiar with the root of the problem, here is the deal:
Gnubg uses decisions for record keeping. For example, to put it simple a move 8/5 6/5 or a double, etc. These decisions are called moverecords. This is a good idea as far as it goes. It is, essentially, what you do when you record a match for somebody else. As you probably know, you need to be careful when recording, but obviously gnubg is that. The moverecords method is used in common file formats, like the popular jellyfish .mat format, and more importantly in the internal .sgf format. Furthermore, the analysis is tied up to these moverecords, and that is what causes us all some headache: a) We cannot analyse a move before it is done, since there will be no moverecord to connect to. The chequerplay and cubehint functionally therefore uses another type of storage (only one hint record containing the current position and the decision is stored). But this causes problems in it self when we save, export or use hint on different positions (moverecords). b) When a position is saved we essentially need a(nother) moverecord that contains the players decision. But currently only records (set positionid, set matchid, etc) defining the position are saved. So as you can see the problem has already been fixed wrongly once in form of the hint storage, and I'm not going to fix it wrongly again. And since fixing it has implications many places in the program and implications for backwards compatibility, it is not something we just do. Christian. On Tue, Jan 27, 2009 at 4:56 PM, Massimiliano Maini <[email protected]> wrote: > > I've queried an italian bg forum about features users would like to see in > gnubg. > Besides already known ones (dB management with pre-built queries and > simplified interface to > build queries), here's an interesting one: > > - gnubg cannot save a position into a sgf file with the associated > analysis/rollout. > > This makes a bit tricky to maintain a collection of interesting positions as > you have to > create them, analyze them and save them as a match. > > MaX. > _______________________________________________ > Bug-gnubg mailing list > [email protected] > http://lists.gnu.org/mailman/listinfo/bug-gnubg > > _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
