Open topic with navigation
WTSupported in traditional Synergy on Windows
AXDEBUG lets you analyze problems in programs that use the Synergy ActiveX API by enabling a debugging system.
One of the following values:
Enable debugging system and log events to a window.
Enable debugging system and log events to the specified file.
Disable debugging system. (default)
Enable debugging system and send debug information to an attached Windows debugger.
On 32-bit Windows, when AXDEBUG is set to YES, the creation of the first ActiveX container creates a debug display, which consists of a tree view of the Synergy DBL/ActiveX system and a log of the related operations. On 64-bit Windows, YES is equivalent to EXTERNAL.
The tree view of ActiveX objects (in the left pane of debug display system when the YES option is used) is not shown for either the FILE=filename or the EXTERNAL option. The FILE and EXTERNAL options only log debug events.
When AXDEBUG is set to FILE=filename, events are logged to a file instead of a window, where filename is the name of the file to which output is appended.
When AXDEBUG is set to EXTERNAL, all debug logging information goes to an attached Windows debugger instead of the debug display. On 64-bit Windows, we recommend using an external debugger.
See Debugging for more information about the debugging system.
The environment or the [synergy], [dbr], or [myprog] section of synergy.ini (where myprog is any .dbr file).
If set at the command prompt,