I'm coming into something that puzzles me. I create a game fragment with variations and it opens fine in Drago. But after selecting a variation line to play using Drago...the variations disappear and only inputs the line for that game and all the branches are lost. Am I doing something wrong or is this a feature limitation, a bug or something that Drago currently doesn't support? Thanks in advance.

Either a bug or something confusing with the interface. Could you send me the sgf file and a description of what you expect to see? (email address in about box).

_________________
Drago is freeware

Then I have to classify this as a bug because this wouldn't be specific to only one specific file that I create using Drago. This happens to *every* SGF file I create using Drago that has variations in the file. For this reason I'm fearful to make variations using Drago at this time. To make variations that I know will still be in the file when I make them I'm now using Mugo, CompoGo and Dariush 6.0. I'm steering clear of making variations in Drago until this is cleared up. This means I only use Drago for playing against GNU Go 3.8...nothing more than this. Once the game is over...I now rely on CompoGo and Mugo mainly for variation branches.

There is one possible reason for this bug. I know that SGF can accommodate making multiple SGF games in one file. I can't confirm this to be the cause..but I think this is where it's getting mixed up. When I create SGF files...I've discovered something interesting. When I create SGF files in Drago, the "Save" button saves the current game. But when I hit "Save as" button using the exact same name of the file being saved...it creates a "branch" of a different file using the SGF extension. In other words...two separate copies of the same game branches in the same file. So when I reopen this file in Drago...variations in that Drago file can become corrupted. This is my speculation as I haven't done debug testing except to note there's a problem with saving variations *after* selecting a line and playing at this point using Drago with GNU Go.

I understand that you use the "start from current position" feature when starting a game against GnuGo. This creates a new tab, extracts the moves from root to current position, send them to GnuGo and starts a game from the position reached. It is not intended to add the moves played during and engine game to an existing game tree (although this has been requested).

This could explain the disappearing variations. In that case, it is not related with editing or saving, but with the interface with game engines.

Does this clarify your problem? I have still to understand how you get "two separate copies of the same game branches in the same file".

_________________
Drago is freeware

I found out how to make separate SGF files using the same file name by accident. I will have to see if I did this in Drago or in Compogo. But either way I don't think playing through a game saved in another Go playing program should affect the ability to see variation branches in Drago. In this case I do find it odd that bringing in these games with branches cause Drago to remove them after selecting a branch to play and then resaving the same file with the same name to suddenly see that the branches are gone when you reopen the file from that point. In my opinion this defeats the purpose of being able to see the branches in Drago but no longer seeing them after resaving the file once the game is over.