qGo has two main windows, one is the client window the other is the board window. Further, there is the debug window, too, but you may not need it.
While handling the connection to internet, negotiating your match requests or looking for games to observe this is your main window. This window appears on starting the qGo program without any of the options -sgf , -sgf19 or filename .
The client window consists of a players list in the upper left, a games list in the upper right, talk windows in the lower left, a restricted message window in the lower right.
Further, there is a single edit line, further referred as command line, on the lower edge and a bar on the right edge containing the hostlist combo box on the top.
Type # at the command line to get a list of internal commands.
Starting any text with # at the command line will parsed as internal command. Nothing is sent to host! E.g. #+dbgwin as internal command.
The Go board is the most important part of the program. It is embedded in the board window. Further the board window contains clocks displaying the remaining times for each player, edit tools and two comment edit windows, a single line field to kibitz online games and a multi line field for receiving comments during online games or commenting games offline.
For fast startup, the command line option -sgf19 , -sgf brings up a local (offline) board to edit a game. If using filename then the file with name filename is loaded immediately. In any case, the main window will not be shown.
Starting any text with # at the single edit line will be sent to client window and parsed as a command (without # ). It is sent to host! Thus, starting with ## will result in a internal command for the client window. E.g. #stats as host command or ##+dbgwin as internal command.
For debugging purposes, the debug window can be shown with the -debug startup option. However, this will set qGo in a debug mode, too, which means the program will run slower.
The debug window is always present but it's maybe hidden. Thus, the debug window a log viewer for qGo. Setting qGo to debug mode means logging more events, especially logging all host responses but some internal messages, too.
Therefore, only opening the debug window doesn't slow down the qGo program.
In order to show the debug window there are other options:
Table 3.2. Debug parameters
|command||where to enter||set mode||debug window|
|-debug||when launching qGo||DEBUG||show|
command line is the bottom most line of the client window .