The debug functions of DOFLinx are designed to help when things are not going as well as you want. There might be a situation where;
- undesirable results are being observed, or;
- an error message of some sort
If you are chasing an issue, or have been asked to create a DEBUG log then keep reading. 
DOFLinx writes a file called DOFLinx.LOG into the current folder where DOFLinx is running. This will be the folder containing DOFLinx.exe or a folder that you specified for the “Start In” within your Windows shortcut.
A DOFLinx.Log file will look something like this;
It is a text file and can be opened in any standard Windows editor. I use Notepad and have that set as my default application for files with the extension LOG.
The debug mode can be set via parameter in your DOFLinx.INI file, ie DEBUG=1
or by sending DOFLinx a message, ie DOFLinxMsg DEBUG=2
There are three modes of debug available, they are;
0 = off, this is normal operation with logging and the debug window disabled
1 = logging is enabled and displaying the DOFLinx window. This mode allows you to see the messages in real time in the message window as well as access the right-click test menu
2 = logging is enabled and not displaying the DOFLinx window. This mode is useful to ensure that both the logging window does not interfere with the focus of various windows, and also to not slow down your system due to lots of scrolling in the debug window.
DOFLinx starts in mode 2, then switches to mode 0 once it reads your INI file unless you give it an alternative command in the INI file or via messaging. DOFLinx needs to start in mode 2 to ensure any messages prior to reading the DEBUG= parameter are logged.
You can change between debug modes at any time. OF course to do that you will have to be sending DOFLinx messages for the new debug level using a tool like DOFLinxMsg.
In addition to creating a LOG file you may have been requested to dump the memory variables when DOFLinx is running, perhaps before and / or after a certain event. There are two ways to dump the DOFLinx memory variables to the DOFLinx.LOG file, they are explained below.
The first option is to have DOFLinx in debug mode 1 and use the right-click menu option as shown below. This can be tricky to do if you are trying to also play a table to a certain point at the same time.
The second option is to use a command line argument, possibly combined with debug in mode 2. This can be done as shown below.
Dumping variables to the DOFLinx.LOG file requires that logging is set to either mode 1 or 2.
Top
are all trademarks of VPFORUMS.