{\rtf1\ansi\ansicpg1252\deff0\deftab720{\fonttbl{\f0\fswiss MS Sans Serif;}{\f1\froman\fcharset2 Symbol;}{\f2\froman Times New Roman;}{\f3\froman\fprq2 Times New Roman;}} {\colortbl\red0\green0\blue0;\red0\green0\blue255;} \deflang1033\horzdoc{\*\fchars }{\*\lchars }\pard\plain\f3\fs48\cf1\b COXTrace Description\plain\f3\fs48\b \par \plain\f3\fs16\b Copyright \'a9 Dundas Software Ltd. 1997-1999, All Rights Reserved \par \plain\f3\fs24 \par COXTrace class gives you additional power that can simplify the process of testing and debugging your applications. \par This class provides all the functionality of TRACE macro but also it allows you to forward trace output into file. The following additional features implemented in the COXTrace class: \par \par \pard\li720\fi-360{\*\pn\pnlvlblt\pnf1\pnindent360{\pntxtb\'b7}}\plain\f3\fs24 {\pntext\f1\'b7\tab}Built-in word wrapping \par {\pntext\f1\'b7\tab}Automatic marking of the start and end of a block of code \par {\pntext\f1\'b7\tab}Automatic indenting of the messages to provide a way to track nesting of COXTrace blocks. \par \pard\plain\f3\fs24 \par All these features simplify the process of reading of output file. E.g. is length of trace message is more than given value (this value can be updated through use of macro) it will be automatically wrapped. Then whenever new COXTrace object is created class we associate new block of trace messages with it. Class traces when object is being destroyed and mark the end of the corresponding block and automatically add trace message that specifies that the end of the block has been reached. This way you can organize your trace messages in logical groups and analyze them independently (like blocks of\~ commands in a programming language). \par \par Moreover COXTrace automatically indents trace messages. Whenever start of block is marked the indention is increased and whenever end of block is marked the indention is decreased. It simplifies the process of reading of trace messages greatly. \par \par COXTrace class has extremely simple interface. First of all you should setup the environment (the name of output file using \plain\f3\fs24\cf1\ul SetDumpFile\plain\f3\fs24 () function plus other COXTrace properties that define the appearance of trace messages). In order to post trace messages you have to \plain\f3\fs24\cf1\ul instantiate\plain\f3\fs24 COXTrace object (the start of new block of trace messages will be marked automatically). Then you can call any of \plain\f3\fs24\cf1\ul Write\plain\f3\fs24 () or \plain\f3\fs24\cf1\ul WriteFormatted\plain\f3\fs24 () functions in order to add new trace messages. When COXTrace object is being \plain\f3\fs24\cf1\ul destroyed\plain\f3\fs24 the end of corresponding block of trace messages will be marked and message that notifies about that event will be posted automatically (like end bracket in C++). \par \par Refer to the \plain\f3\fs24\b AdvancedTrace\plain\f3\fs24 sample found in .\\Samples\\Utility\\AdvancedTrace subdirectory of your Ultimate Toolbox directory for example of different ways you can use COXTrace class. \par \~ \par \plain\f3\fs28\b Dependencies \par \plain\f3\fs24 #include "OXTrace.h" \par \~ \par \pard\plain\lang4105\f2\fs20 \par }