<Comment># Doxyfile 1.8.11</Comment><br/>
<Error></Error><br/>
<Comment># This file describes the settings to be used by the documentation system</Comment><br/>
<Comment># doxygen (www.doxygen.org) for a project.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># All text after a double hash (##) is considered a comment and is placed in</Comment><br/>
<Comment># front of the TAG it is preceding.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># All text after a single hash (#) is considered a comment and will be ignored.</Comment><br/>
<Comment># The format is:</Comment><br/>
<Comment># TAG = value [value, ...]</Comment><br/>
<Comment># For lists, items can also be appended using:</Comment><br/>
<Comment># TAG += value [value, ...]</Comment><br/>
<Comment># Values that contain spaces should be placed between quotes (\" \").</Comment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Project related configuration options</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># This tag specifies the encoding used for all characters in the config file</Comment><br/>
<Comment># that follow. The default is UTF-8 which is also the encoding used for all text</Comment><br/>
<Comment># before the first occurrence of this tag. Doxygen uses libiconv (or the iconv</Comment><br/>
<Comment># built into libc) for the transcoding. See http://www.gnu.org/software/libiconv</Comment><br/>
<Comment># for the list of possible encodings.</Comment><br/>
<Comment># The default value is: UTF-8.</Comment><br/>
<Error></Error><br/>
<Keyword>DOXYFILE_ENCODING</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> UTF-8</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>PROJECT_NAME</KeywordInComment><Comment> tag is a single word (or a sequence of words surrounded by</Comment><br/>
<Comment># double-quotes, unless you are using Doxywizard) that should identify the</Comment><br/>
<Comment># project for which the documentation is generated. This name is used in the</Comment><br/>
<Comment># title of most generated pages and in a few other places.</Comment><br/>
<Comment># The default value is: My Project.</Comment><br/>
<Error></Error><br/>
<Keyword>PROJECT_NAME</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> "My Project"</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>PROJECT_NUMBER</KeywordInComment><Comment> tag can be used to enter a project or revision number. This</Comment><br/>
<Comment># could be handy for archiving the generated documentation or if some version</Comment><br/>
<Comment># control system is used.</Comment><br/>
<Error></Error><br/>
<Keyword>PROJECT_NUMBER</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># Using the </Comment><KeywordInComment>PROJECT_BRIEF</KeywordInComment><Comment> tag one can provide an optional one line description</Comment><br/>
<Comment># for a project that appears at the top of each page and should give viewer a</Comment><br/>
<Comment># quick idea about the purpose of the project. Keep the description short.</Comment><br/>
<Error></Error><br/>
<Keyword>PROJECT_BRIEF</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># With the </Comment><KeywordInComment>PROJECT_LOGO</KeywordInComment><Comment> tag one can specify a logo or an icon that is included</Comment><br/>
<Comment># in the documentation. The maximum height of the logo should not exceed 55</Comment><br/>
<Comment># pixels and the maximum width should not exceed 200 pixels. Doxygen will copy</Comment><br/>
<Comment># the logo to the output directory.</Comment><br/>
<Error></Error><br/>
<Keyword>PROJECT_LOGO</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> tag is used to specify the (relative or absolute) path</Comment><br/>
<Comment># into which the generated documentation will be written. If a relative path is</Comment><br/>
<Comment># entered, it will be relative to the location where doxygen was started. If</Comment><br/>
<Comment># left blank the current directory will be used.</Comment><br/>
<Error></Error><br/>
<Keyword>OUTPUT_DIRECTORY</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>CREATE_SUBDIRS</KeywordInComment><Comment> tag is set to YES then doxygen will create 4096 sub-</Comment><br/>
<Comment># directories (in 2 levels) under the output directory of each output format and</Comment><br/>
<Comment># will distribute the generated files over these directories. Enabling this</Comment><br/>
<Comment># option can be useful when feeding doxygen a huge amount of source files, where</Comment><br/>
<Comment># putting all generated files in the same directory would otherwise causes</Comment><br/>
<Comment># performance problems for the file system.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>CREATE_SUBDIRS</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>ALLOW_UNICODE_NAMES</KeywordInComment><Comment> tag is set to YES, doxygen will allow non-ASCII</Comment><br/>
<Comment># characters to appear in the names of generated files. If set to NO, non-ASCII</Comment><br/>
<Comment># characters will be escaped, for example _xE3_x81_x84 will be used for Unicode</Comment><br/>
<Comment># U+3044.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>ALLOW_UNICODE_NAMES</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>OUTPUT_LANGUAGE</KeywordInComment><Comment> tag is used to specify the language in which all</Comment><br/>
<Comment># documentation generated by doxygen is written. Doxygen will use this</Comment><br/>
<Comment># information to generate all constant output in the proper language.</Comment><br/>
<Comment># Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese,</Comment><br/>
<Comment># Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),</Comment><br/>
<Comment># Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian,</Comment><br/>
<Comment># Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),</Comment><br/>
<Comment># Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,</Comment><br/>
<Comment># Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian,</Comment><br/>
<Comment># Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,</Comment><br/>
<Comment># Ukrainian and Vietnamese.</Comment><br/>
<Comment># The default value is: English.</Comment><br/>
<Error></Error><br/>
<Keyword>OUTPUT_LANGUAGE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> English</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>BRIEF_MEMBER_DESC</KeywordInComment><Comment> tag is set to YES, doxygen will include brief member</Comment><br/>
<Comment># descriptions after the members that are listed in the file and class</Comment><br/>
<Comment># documentation (similar to Javadoc). Set to NO to disable this.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>BRIEF_MEMBER_DESC</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>REPEAT_BRIEF</KeywordInComment><Comment> tag is set to YES, doxygen will prepend the brief</Comment><br/>
<Comment># description of a member or function before the detailed description</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note: If both </Comment><KeywordInComment>HIDE_UNDOC_MEMBERS</KeywordInComment><Comment> and </Comment><KeywordInComment>BRIEF_MEMBER_DESC</KeywordInComment><Comment> are set to NO, the</Comment><br/>
<Comment># brief descriptions will be completely suppressed.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>REPEAT_BRIEF</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># This tag implements a quasi-intelligent brief description abbreviator that is</Comment><br/>
<Comment># used to form the text in various listings. Each string in this list, if found</Comment><br/>
<Comment># as the leading text of the brief description, will be stripped from the text</Comment><br/>
<Comment># and the result, after processing the whole list, is used as the annotated</Comment><br/>
<Comment># text. Otherwise, the brief description is used as-is. If left blank, the</Comment><br/>
<Comment># following values are used ($name is automatically replaced with the name of</Comment><br/>
<Comment># the entity):The $name class, The $name widget, The $name file, is, provides,</Comment><br/>
<Comment># specifies, contains, represents, a, an and the.</Comment><br/>
<Error></Error><br/>
<Keyword>ABBREVIATE_BRIEF</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>ALWAYS_DETAILED_SEC</KeywordInComment><Comment> and </Comment><KeywordInComment>REPEAT_BRIEF</KeywordInComment><Comment> tags are both set to YES then</Comment><br/>
<Comment># doxygen will generate a detailed section even if there is only a brief</Comment><br/>
<Comment># description.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>ALWAYS_DETAILED_SEC</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>INLINE_INHERITED_MEMB</KeywordInComment><Comment> tag is set to YES, doxygen will show all</Comment><br/>
<Comment># inherited members of a class in the documentation of that class as if those</Comment><br/>
<Comment># members were ordinary class members. Constructors, destructors and assignment</Comment><br/>
<Comment># operators of the base classes will not be shown.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>INLINE_INHERITED_MEMB</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>FULL_PATH_NAMES</KeywordInComment><Comment> tag is set to YES, doxygen will prepend the full path</Comment><br/>
<Comment># before files name in the file list and in the header files. If set to NO the</Comment><br/>
<Comment># shortest path that makes the file name unique will be used</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>FULL_PATH_NAMES</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>STRIP_FROM_PATH</KeywordInComment><Comment> tag can be used to strip a user-defined part of the path.</Comment><br/>
<Comment># Stripping is only done if one of the specified strings matches the left-hand</Comment><br/>
<Comment># part of the path. The tag can be used to show relative paths in the file list.</Comment><br/>
<Comment># If left blank the directory from which doxygen is run is used as the path to</Comment><br/>
<Comment># strip.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that you can specify absolute paths here, but also relative paths, which</Comment><br/>
<Comment># will be relative from the directory where doxygen is started.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>FULL_PATH_NAMES</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>STRIP_FROM_PATH</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>STRIP_FROM_INC_PATH</KeywordInComment><Comment> tag can be used to strip a user-defined part of the</Comment><br/>
<Comment># path mentioned in the documentation of a class, which tells the reader which</Comment><br/>
<Comment># header file to include in order to use a class. If left blank only the name of</Comment><br/>
<Comment># the header file containing the class definition is used. Otherwise one should</Comment><br/>
<Comment># specify the list of include paths that are normally passed to the compiler</Comment><br/>
<Comment># using the -I flag.</Comment><br/>
<Error></Error><br/>
<Keyword>STRIP_FROM_INC_PATH</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SHORT_NAMES</KeywordInComment><Comment> tag is set to YES, doxygen will generate much shorter (but</Comment><br/>
<Comment># less readable) file names. This can be useful is your file systems doesn't</Comment><br/>
<Comment># support long names like on DOS, Mac, or CD-ROM.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SHORT_NAMES</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>JAVADOC_AUTOBRIEF</KeywordInComment><Comment> tag is set to YES then doxygen will interpret the</Comment><br/>
<Comment># first line (until the first dot) of a Javadoc-style comment as the brief</Comment><br/>
<Comment># description. If set to NO, the Javadoc-style will behave just like regular Qt-</Comment><br/>
<Comment># style comments (thus requiring an explicit @brief command for a brief</Comment><br/>
<Comment># description.)</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>JAVADOC_AUTOBRIEF</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>QT_AUTOBRIEF</KeywordInComment><Comment> tag is set to YES then doxygen will interpret the first</Comment><br/>
<Comment># line (until the first dot) of a Qt-style comment as the brief description. If</Comment><br/>
<Comment># set to NO, the Qt-style will behave just like regular Qt-style comments (thus</Comment><br/>
<Comment># requiring an explicit \brief command for a brief description.)</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>QT_AUTOBRIEF</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MULTILINE_CPP_IS_BRIEF</KeywordInComment><Comment> tag can be set to YES to make doxygen treat a</Comment><br/>
<Comment># multi-line C++ special comment block (i.e. a block of //! or /// comments) as</Comment><br/>
<Comment># a brief description. This used to be the default behavior. The new default is</Comment><br/>
<Comment># to treat a multi-line C++ comment block as a detailed description. Set this</Comment><br/>
<Comment># tag to YES if you prefer the old behavior instead.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that setting this tag to YES also means that rational rose comments are</Comment><br/>
<Comment># not recognized any more.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>MULTILINE_CPP_IS_BRIEF</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>INHERIT_DOCS</KeywordInComment><Comment> tag is set to YES then an undocumented member inherits the</Comment><br/>
<Comment># documentation from any documented member that it re-implements.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INHERIT_DOCS</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SEPARATE_MEMBER_PAGES</KeywordInComment><Comment> tag is set to YES then doxygen will produce a new</Comment><br/>
<Comment># page for each member. If set to NO, the documentation of a member will be part</Comment><br/>
<Comment># of the file/class/namespace that contains it.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SEPARATE_MEMBER_PAGES</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>TAB_SIZE</KeywordInComment><Comment> tag can be used to set the number of spaces in a tab. Doxygen</Comment><br/>
<Comment># uses this value to replace tabs by spaces in code fragments.</Comment><br/>
<Comment># Minimum value: 1, maximum value: 16, default value: 4.</Comment><br/>
<Error></Error><br/>
<Keyword>TAB_SIZE</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><UntypedValue> 4</UntypedValue><br/>
<Error></Error><br/>
<Comment># This tag can be used to specify a number of </Comment><KeywordInComment>aliases</KeywordInComment><Comment> that act as commands in</Comment><br/>
<Comment># the documentation. An alias has the form:</Comment><br/>
<Comment># name=value</Comment><br/>
<Comment># For example adding</Comment><br/>
<Comment># "sideeffect=@par Side Effects:\n"</Comment><br/>
<Comment># will allow you to put the command \sideeffect (or @sideeffect) in the</Comment><br/>
<Comment># documentation, which will result in a user-defined paragraph with heading</Comment><br/>
<Comment># "Side Effects:". You can put \n's in the value part of an alias to insert</Comment><br/>
<Comment># newlines.</Comment><br/>
<Error></Error><br/>
<Keyword>ALIASES</Keyword><Normal Text>                </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># This tag can be used to specify a number of word-keyword mappings (TCL only).</Comment><br/>
<Comment># A mapping has the form "name=value". For example adding "class=itcl::class"</Comment><br/>
<Comment># will allow you to use the command class in the itcl::class meaning.</Comment><br/>
<Error></Error><br/>
<Keyword>TCL_SUBST</Keyword><Normal Text>              </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>OPTIMIZE_OUTPUT_FOR_C</KeywordInComment><Comment> tag to YES if your project consists of C sources</Comment><br/>
<Comment># only. Doxygen will then generate output that is more tailored for C. For</Comment><br/>
<Comment># instance, some of the names that are used will be different. The list of all</Comment><br/>
<Comment># members will be omitted, etc.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>OPTIMIZE_OUTPUT_FOR_C</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>OPTIMIZE_OUTPUT_JAVA</KeywordInComment><Comment> tag to YES if your project consists of Java or</Comment><br/>
<Comment># Python sources only. Doxygen will then generate output that is more tailored</Comment><br/>
<Comment># for that language. For instance, namespaces will be presented as packages,</Comment><br/>
<Comment># qualified scopes will look different, etc.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>OPTIMIZE_OUTPUT_JAVA</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>OPTIMIZE_FOR_FORTRAN</KeywordInComment><Comment> tag to YES if your project consists of Fortran</Comment><br/>
<Comment># sources. Doxygen will then generate output that is tailored for Fortran.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>OPTIMIZE_FOR_FORTRAN</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>OPTIMIZE_OUTPUT_VHDL</KeywordInComment><Comment> tag to YES if your project consists of VHDL</Comment><br/>
<Comment># sources. Doxygen will then generate output that is tailored for VHDL.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>OPTIMIZE_OUTPUT_VHDL</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Doxygen selects the parser to use depending on the extension of the files it</Comment><br/>
<Comment># parses. With this tag you can assign which parser to use for a given</Comment><br/>
<Comment># extension. Doxygen has a built-in mapping, but you can override or extend it</Comment><br/>
<Comment># using this tag. The format is ext=language, where ext is a file extension, and</Comment><br/>
<Comment># language is one of the parsers supported by doxygen: IDL, Java, Javascript,</Comment><br/>
<Comment># C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:</Comment><br/>
<Comment># FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran:</Comment><br/>
<Comment># Fortran. In the later case the parser tries to guess whether the code is fixed</Comment><br/>
<Comment># or free formatted code, this is the default for Fortran type files), VHDL. For</Comment><br/>
<Comment># instance to make doxygen treat .inc files as Fortran files (default is PHP),</Comment><br/>
<Comment># and .f files as C (default is Fortran), use: inc=Fortran f=C.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note: For files without extension you can use no_extension as a placeholder.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that for custom extensions you also need to set </Comment><KeywordInComment>FILE_PATTERNS</KeywordInComment><Comment> otherwise</Comment><br/>
<Comment># the files are not read by doxygen.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTENSION_MAPPING</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>MARKDOWN_SUPPORT</KeywordInComment><Comment> tag is enabled then doxygen pre-processes all comments</Comment><br/>
<Comment># according to the Markdown format, which allows for more readable</Comment><br/>
<Comment># documentation. See http://daringfireball.net/projects/markdown/ for details.</Comment><br/>
<Comment># The output of markdown processing is further processed by doxygen, so you can</Comment><br/>
<Comment># mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in</Comment><br/>
<Comment># case of backward compatibilities issues.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MARKDOWN_SUPPORT</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># When enabled doxygen tries to link words that correspond to documented</Comment><br/>
<Comment># classes, or namespaces to their corresponding documentation. Such a link can</Comment><br/>
<Comment># be prevented in individual cases by putting a % sign in front of the word or</Comment><br/>
<Comment># globally by setting </Comment><KeywordInComment>AUTOLINK_SUPPORT</KeywordInComment><Comment> to NO.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>AUTOLINK_SUPPORT</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If you use STL classes (i.e. std::string, std::vector, etc.) but do not want</Comment><br/>
<Comment># to include (a tag file for) the STL sources as </Comment><KeywordInComment>input</KeywordInComment><Comment>, then you should set this</Comment><br/>
<Comment># tag to YES in order to let doxygen match functions declarations and</Comment><br/>
<Comment># definitions whose arguments contain STL classes (e.g. func(std::string);</Comment><br/>
<Comment># versus func(std::string) {}). This also make the inheritance and collaboration</Comment><br/>
<Comment># diagrams that involve STL classes more complete and accurate.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>BUILTIN_STL_SUPPORT</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If you use Microsoft's C++/CLI language, you should set this option to YES to</Comment><br/>
<Comment># enable parsing support.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>CPP_CLI_SUPPORT</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>SIP_SUPPORT</KeywordInComment><Comment> tag to YES if your project consists of sip (see:</Comment><br/>
<Comment># http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen</Comment><br/>
<Comment># will parse them like normal C++ but will assume all classes use public instead</Comment><br/>
<Comment># of private inheritance when no explicit protection keyword is present.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SIP_SUPPORT</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># For Microsoft's IDL there are propget and propput attributes to indicate</Comment><br/>
<Comment># getter and setter methods for a property. Setting this option to YES will make</Comment><br/>
<Comment># doxygen to replace the get and set methods by a property in the documentation.</Comment><br/>
<Comment># This will only work if the methods are indeed getting or setting a simple</Comment><br/>
<Comment># type. If this is not the case, or you want to show the methods anyway, you</Comment><br/>
<Comment># should set this option to NO.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>IDL_PROPERTY_SUPPORT</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If member grouping is used in the documentation and the </Comment><KeywordInComment>DISTRIBUTE_GROUP_DOC</KeywordInComment><br/>
<Comment># tag is set to YES then doxygen will reuse the documentation of the first</Comment><br/>
<Comment># member in the group (if any) for the other members of the group. By default</Comment><br/>
<Comment># all members of a group must be documented explicitly.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>DISTRIBUTE_GROUP_DOC</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If one adds a struct or class to a group and this option is enabled, then also</Comment><br/>
<Comment># any nested class or struct is added to the same group. By default this option</Comment><br/>
<Comment># is disabled and one has to add nested compounds explicitly via \ingroup.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GROUP_NESTED_COMPOUNDS</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>SUBGROUPING</KeywordInComment><Comment> tag to YES to allow class member groups of the same type</Comment><br/>
<Comment># (for instance a group of public functions) to be put as a subgroup of that</Comment><br/>
<Comment># type (e.g. under the Public Functions section). Set it to NO to prevent</Comment><br/>
<Comment># </Comment><KeywordInComment>subgrouping</KeywordInComment><Comment>. Alternatively, this can be done per class using the</Comment><br/>
<Comment># \nosubgrouping command.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SUBGROUPING</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># When the </Comment><KeywordInComment>INLINE_GROUPED_CLASSES</KeywordInComment><Comment> tag is set to YES, classes, structs and unions</Comment><br/>
<Comment># are shown inside the group in which they are included (e.g. using \ingroup)</Comment><br/>
<Comment># instead of on a separate page (for HTML and Man pages) or section (for LaTeX</Comment><br/>
<Comment># and RTF).</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that this feature does not work in combination with</Comment><br/>
<Comment># </Comment><KeywordInComment>SEPARATE_MEMBER_PAGES</KeywordInComment><Comment>.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>INLINE_GROUPED_CLASSES</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># When the </Comment><KeywordInComment>INLINE_SIMPLE_STRUCTS</KeywordInComment><Comment> tag is set to YES, structs, classes, and unions</Comment><br/>
<Comment># with only public data fields or simple typedef fields will be shown inline in</Comment><br/>
<Comment># the documentation of the scope in which they are defined (i.e. file,</Comment><br/>
<Comment># namespace, or group documentation), provided this scope is documented. If set</Comment><br/>
<Comment># to NO, structs, classes, and unions are shown on a separate page (for HTML and</Comment><br/>
<Comment># Man pages) or section (for LaTeX and RTF).</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>INLINE_SIMPLE_STRUCTS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># When </Comment><KeywordInComment>TYPEDEF_HIDES_STRUCT</KeywordInComment><Comment> tag is enabled, a typedef of a struct, union, or</Comment><br/>
<Comment># enum is documented as struct, union, or enum with the name of the typedef. So</Comment><br/>
<Comment># typedef struct TypeS {} TypeT, will appear in the documentation as a struct</Comment><br/>
<Comment># with name TypeT. When disabled the typedef will appear as a member of a file,</Comment><br/>
<Comment># namespace, or class. And the struct will be named TypeS. This can typically be</Comment><br/>
<Comment># useful for C code in case the coding convention dictates that all compound</Comment><br/>
<Comment># types are typedef'ed and only the typedef is referenced, never the tag name.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>TYPEDEF_HIDES_STRUCT</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The size of the symbol lookup cache can be set using </Comment><KeywordInComment>LOOKUP_CACHE_SIZE</KeywordInComment><Comment>. This</Comment><br/>
<Comment># cache is used to resolve symbols given their name and scope. Since this can be</Comment><br/>
<Comment># an expensive process and often the same symbol appears multiple times in the</Comment><br/>
<Comment># code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small</Comment><br/>
<Comment># doxygen will become slower. If the cache is too large, memory is wasted. The</Comment><br/>
<Comment># cache size is given by this formula: 2^(16+</Comment><KeywordInComment>LOOKUP_CACHE_SIZE</KeywordInComment><Comment>). The valid range</Comment><br/>
<Comment># is 0..9, the default is 0, corresponding to a cache size of 2^16=65536</Comment><br/>
<Comment># symbols. At the end of a run doxygen will report the cache usage and suggest</Comment><br/>
<Comment># the optimal cache size from a speed point of view.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 9, default value: 0.</Comment><br/>
<Error></Error><br/>
<Keyword>LOOKUP_CACHE_SIZE</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> 0</UntypedValue><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Build related configuration options</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTRACT_ALL</KeywordInComment><Comment> tag is set to YES, doxygen will assume all entities in</Comment><br/>
<Comment># documentation are documented, even if no documentation was available. Private</Comment><br/>
<Comment># class members and static file members will be hidden unless the</Comment><br/>
<Comment># </Comment><KeywordInComment>EXTRACT_PRIVATE</KeywordInComment><Comment> respectively </Comment><KeywordInComment>EXTRACT_STATIC</KeywordInComment><Comment> tags are set to YES.</Comment><br/>
<Comment># Note: This will also disable the </Comment><KeywordInComment>warnings</KeywordInComment><Comment> about undocumented members that are</Comment><br/>
<Comment># normally produced when </Comment><KeywordInComment>WARNINGS</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_ALL</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTRACT_PRIVATE</KeywordInComment><Comment> tag is set to YES, all private members of a class will</Comment><br/>
<Comment># be included in the documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_PRIVATE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTRACT_PACKAGE</KeywordInComment><Comment> tag is set to YES, all members with package or internal</Comment><br/>
<Comment># scope will be included in the documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_PACKAGE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTRACT_STATIC</KeywordInComment><Comment> tag is set to YES, all static members of a file will be</Comment><br/>
<Comment># included in the documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_STATIC</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTRACT_LOCAL_CLASSES</KeywordInComment><Comment> tag is set to YES, classes (and structs) defined</Comment><br/>
<Comment># locally in source files will be included in the documentation. If set to NO,</Comment><br/>
<Comment># only classes defined in header files are included. Does not have any effect</Comment><br/>
<Comment># for Java sources.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_LOCAL_CLASSES</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># This flag is only useful for Objective-C code. If set to YES, local methods,</Comment><br/>
<Comment># which are defined in the implementation section but not in the interface are</Comment><br/>
<Comment># included in the documentation. If set to NO, only methods in the interface are</Comment><br/>
<Comment># included.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_LOCAL_METHODS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If this flag is set to YES, the members of anonymous namespaces will be</Comment><br/>
<Comment># extracted and appear in the documentation as a namespace called</Comment><br/>
<Comment># 'anonymous_namespace{file}', where file will be replaced with the base name of</Comment><br/>
<Comment># the file that contains the anonymous namespace. By default anonymous namespace</Comment><br/>
<Comment># are hidden.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRACT_ANON_NSPACES</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HIDE_UNDOC_MEMBERS</KeywordInComment><Comment> tag is set to YES, doxygen will hide all</Comment><br/>
<Comment># undocumented members inside documented classes or files. If set to NO these</Comment><br/>
<Comment># members will be included in the various overviews, but no documentation</Comment><br/>
<Comment># section is generated. This option has no effect if </Comment><KeywordInComment>EXTRACT_ALL</KeywordInComment><Comment> is enabled.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_UNDOC_MEMBERS</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HIDE_UNDOC_CLASSES</KeywordInComment><Comment> tag is set to YES, doxygen will hide all</Comment><br/>
<Comment># undocumented classes that are normally visible in the class hierarchy. If set</Comment><br/>
<Comment># to NO, these classes will be included in the various overviews. This option</Comment><br/>
<Comment># has no effect if </Comment><KeywordInComment>EXTRACT_ALL</KeywordInComment><Comment> is enabled.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_UNDOC_CLASSES</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HIDE_FRIEND_COMPOUNDS</KeywordInComment><Comment> tag is set to YES, doxygen will hide all friend</Comment><br/>
<Comment># (class|struct|union) declarations. If set to NO, these declarations will be</Comment><br/>
<Comment># included in the documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_FRIEND_COMPOUNDS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HIDE_IN_BODY_DOCS</KeywordInComment><Comment> tag is set to YES, doxygen will hide any</Comment><br/>
<Comment># documentation blocks found inside the body of a function. If set to NO, these</Comment><br/>
<Comment># blocks will be appended to the function's detailed documentation block.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_IN_BODY_DOCS</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>INTERNAL_DOCS</KeywordInComment><Comment> tag determines if documentation that is typed after a</Comment><br/>
<Comment># \internal command is included. If the tag is set to NO then the documentation</Comment><br/>
<Comment># will be excluded. Set it to YES to include the internal documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>INTERNAL_DOCS</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>CASE_SENSE_NAMES</KeywordInComment><Comment> tag is set to NO then doxygen will only generate file</Comment><br/>
<Comment># names in lower-case letters. If set to YES, upper-case letters are also</Comment><br/>
<Comment># allowed. This is useful if you have classes or files whose names only differ</Comment><br/>
<Comment># in case and if your file system supports case sensitive file names. Windows</Comment><br/>
<Comment># and Mac users are advised to set this option to NO.</Comment><br/>
<Comment># The default value is: system dependent.</Comment><br/>
<Error></Error><br/>
<Keyword>CASE_SENSE_NAMES</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HIDE_SCOPE_NAMES</KeywordInComment><Comment> tag is set to NO then doxygen will show members with</Comment><br/>
<Comment># their full class and namespace scopes in the documentation. If set to YES, the</Comment><br/>
<Comment># scope will be hidden.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_SCOPE_NAMES</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HIDE_COMPOUND_REFERENCE</KeywordInComment><Comment> tag is set to NO (default) then doxygen will</Comment><br/>
<Comment># append additional text to a page's title, such as Class Reference. If set to</Comment><br/>
<Comment># YES the compound reference will be hidden.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_COMPOUND_REFERENCE</Keyword><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SHOW_INCLUDE_FILES</KeywordInComment><Comment> tag is set to YES then doxygen will put a list of</Comment><br/>
<Comment># the files that are included by a file in the documentation of that file.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SHOW_INCLUDE_FILES</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SHOW_GROUPED_MEMB_INC</KeywordInComment><Comment> tag is set to YES then Doxygen will add for each</Comment><br/>
<Comment># grouped member an include statement to the documentation, telling the reader</Comment><br/>
<Comment># which file to include in order to use the member.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SHOW_GROUPED_MEMB_INC</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>FORCE_LOCAL_INCLUDES</KeywordInComment><Comment> tag is set to YES then doxygen will list include</Comment><br/>
<Comment># files with double quotes in the documentation rather than with sharp brackets.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>FORCE_LOCAL_INCLUDES</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>INLINE_INFO</KeywordInComment><Comment> tag is set to YES then a tag [inline] is inserted in the</Comment><br/>
<Comment># documentation for inline members.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INLINE_INFO</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SORT_MEMBER_DOCS</KeywordInComment><Comment> tag is set to YES then doxygen will sort the</Comment><br/>
<Comment># (detailed) documentation of file and class members alphabetically by member</Comment><br/>
<Comment># name. If set to NO, the members will appear in declaration order.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SORT_MEMBER_DOCS</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SORT_BRIEF_DOCS</KeywordInComment><Comment> tag is set to YES then doxygen will sort the brief</Comment><br/>
<Comment># descriptions of file, namespace and class members alphabetically by member</Comment><br/>
<Comment># name. If set to NO, the members will appear in declaration order. Note that</Comment><br/>
<Comment># this will also influence the order of the classes in the class list.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SORT_BRIEF_DOCS</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SORT_MEMBERS_CTORS_1ST</KeywordInComment><Comment> tag is set to YES then doxygen will sort the</Comment><br/>
<Comment># (brief and detailed) documentation of class members so that constructors and</Comment><br/>
<Comment># destructors are listed first. If set to NO the constructors will appear in the</Comment><br/>
<Comment># respective orders defined by </Comment><KeywordInComment>SORT_BRIEF_DOCS</KeywordInComment><Comment> and </Comment><KeywordInComment>SORT_MEMBER_DOCS</KeywordInComment><Comment>.</Comment><br/>
<Comment># Note: If </Comment><KeywordInComment>SORT_BRIEF_DOCS</KeywordInComment><Comment> is set to NO this option is ignored for sorting brief</Comment><br/>
<Comment># member documentation.</Comment><br/>
<Comment># Note: If </Comment><KeywordInComment>SORT_MEMBER_DOCS</KeywordInComment><Comment> is set to NO this option is ignored for sorting</Comment><br/>
<Comment># detailed member documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SORT_MEMBERS_CTORS_1ST</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SORT_GROUP_NAMES</KeywordInComment><Comment> tag is set to YES then doxygen will sort the hierarchy</Comment><br/>
<Comment># of group names into alphabetical order. If set to NO the group names will</Comment><br/>
<Comment># appear in their defined order.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SORT_GROUP_NAMES</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SORT_BY_SCOPE_NAME</KeywordInComment><Comment> tag is set to YES, the class list will be sorted by</Comment><br/>
<Comment># fully-qualified names, including namespaces. If set to NO, the class list will</Comment><br/>
<Comment># be sorted only by class name, not including the namespace part.</Comment><br/>
<Comment># Note: This option is not very useful if </Comment><KeywordInComment>HIDE_SCOPE_NAMES</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Comment># Note: This option applies only to the class list, not to the alphabetical</Comment><br/>
<Comment># list.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SORT_BY_SCOPE_NAME</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>STRICT_PROTO_MATCHING</KeywordInComment><Comment> option is enabled and doxygen fails to do proper</Comment><br/>
<Comment># type resolution of all parameters of a function it will reject a match between</Comment><br/>
<Comment># the prototype and the implementation of a member function even if there is</Comment><br/>
<Comment># only one candidate or it is obvious which candidate to choose by doing a</Comment><br/>
<Comment># simple string match. By disabling </Comment><KeywordInComment>STRICT_PROTO_MATCHING</KeywordInComment><Comment> doxygen will still</Comment><br/>
<Comment># accept a match between prototype and implementation in such cases.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>STRICT_PROTO_MATCHING</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>GENERATE_TODOLIST</KeywordInComment><Comment> tag can be used to enable (YES) or disable (NO) the todo</Comment><br/>
<Comment># list. This list is created by putting \todo commands in the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_TODOLIST</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>GENERATE_TESTLIST</KeywordInComment><Comment> tag can be used to enable (YES) or disable (NO) the test</Comment><br/>
<Comment># list. This list is created by putting \test commands in the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_TESTLIST</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>GENERATE_BUGLIST</KeywordInComment><Comment> tag can be used to enable (YES) or disable (NO) the bug</Comment><br/>
<Comment># list. This list is created by putting \bug commands in the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_BUGLIST</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>GENERATE_DEPRECATEDLIST</KeywordInComment><Comment> tag can be used to enable (YES) or disable (NO)</Comment><br/>
<Comment># the deprecated list. This list is created by putting \deprecated commands in</Comment><br/>
<Comment># the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_DEPRECATEDLIST</Keyword><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>ENABLED_SECTIONS</KeywordInComment><Comment> tag can be used to enable conditional documentation</Comment><br/>
<Comment># sections, marked by \if <section_label> ... \endif and \cond <section_label></Comment><br/>
<Comment># ... \endcond blocks.</Comment><br/>
<Error></Error><br/>
<Keyword>ENABLED_SECTIONS</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MAX_INITIALIZER_LINES</KeywordInComment><Comment> tag determines the maximum number of lines that the</Comment><br/>
<Comment># initial value of a variable or macro / define can have for it to appear in the</Comment><br/>
<Comment># documentation. If the initializer consists of more lines than specified here</Comment><br/>
<Comment># it will be hidden. Use a value of 0 to hide initializers completely. The</Comment><br/>
<Comment># appearance of the value of individual variables and macros / defines can be</Comment><br/>
<Comment># controlled using \showinitializer or \hideinitializer command in the</Comment><br/>
<Comment># documentation regardless of this setting.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 10000, default value: 30.</Comment><br/>
<Error></Error><br/>
<Keyword>MAX_INITIALIZER_LINES</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> 30</UntypedValue><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>SHOW_USED_FILES</KeywordInComment><Comment> tag to NO to disable the list of files generated at</Comment><br/>
<Comment># the bottom of the documentation of classes and structs. If set to YES, the</Comment><br/>
<Comment># list will mention the files that were used to generate the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SHOW_USED_FILES</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>SHOW_FILES</KeywordInComment><Comment> tag to NO to disable the generation of the Files page. This</Comment><br/>
<Comment># will remove the Files entry from the Quick Index and from the Folder Tree View</Comment><br/>
<Comment># (if specified).</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SHOW_FILES</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>SHOW_NAMESPACES</KeywordInComment><Comment> tag to NO to disable the generation of the Namespaces</Comment><br/>
<Comment># page. This will remove the Namespaces entry from the Quick Index and from the</Comment><br/>
<Comment># Folder Tree View (if specified).</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SHOW_NAMESPACES</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>FILE_VERSION_FILTER</KeywordInComment><Comment> tag can be used to specify a program or script that</Comment><br/>
<Comment># doxygen should invoke to get the current version for each file (typically from</Comment><br/>
<Comment># the version control system). Doxygen will invoke the program by executing (via</Comment><br/>
<Comment># popen()) the command command </Comment><KeywordInComment>input</KeywordInComment><Comment>-file, where command is the value of the</Comment><br/>
<Comment># </Comment><KeywordInComment>FILE_VERSION_FILTER</KeywordInComment><Comment> tag, and </Comment><KeywordInComment>input</KeywordInComment><Comment>-file is the name of an </Comment><KeywordInComment>input</KeywordInComment><Comment> file provided</Comment><br/>
<Comment># by doxygen. Whatever the program writes to standard output is used as the file</Comment><br/>
<Comment># version. For an example see the documentation.</Comment><br/>
<Error></Error><br/>
<Keyword>FILE_VERSION_FILTER</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LAYOUT_FILE</KeywordInComment><Comment> tag can be used to specify a layout file which will be parsed</Comment><br/>
<Comment># by doxygen. The layout file controls the global structure of the generated</Comment><br/>
<Comment># output files in an output format independent way. To create the layout file</Comment><br/>
<Comment># that represents doxygen's defaults, run doxygen with the -l option. You can</Comment><br/>
<Comment># optionally specify a file name after the option, if omitted DoxygenLayout.xml</Comment><br/>
<Comment># will be used as the name of the layout file.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that if you run doxygen from a directory containing a file called</Comment><br/>
<Comment># DoxygenLayout.xml, doxygen will parse it automatically even if the </Comment><KeywordInComment>LAYOUT_FILE</KeywordInComment><br/>
<Comment># tag is left empty.</Comment><br/>
<Error></Error><br/>
<Keyword>LAYOUT_FILE</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>CITE_BIB_FILES</KeywordInComment><Comment> tag can be used to specify one or more bib files containing</Comment><br/>
<Comment># the reference definitions. This must be a list of .bib files. The .bib</Comment><br/>
<Comment># extension is automatically appended if omitted. This requires the bibtex tool</Comment><br/>
<Comment># to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info.</Comment><br/>
<Comment># For LaTeX the style of the bibliography can be controlled using</Comment><br/>
<Comment># </Comment><KeywordInComment>LATEX_BIB_STYLE</KeywordInComment><Comment>. To use this feature you need bibtex and perl available in the</Comment><br/>
<Comment># search path. See also \cite for info how to create references.</Comment><br/>
<Error></Error><br/>
<Keyword>CITE_BIB_FILES</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to warning and progress messages</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>QUIET</KeywordInComment><Comment> tag can be used to turn on/off the messages that are generated to</Comment><br/>
<Comment># standard output by doxygen. If </Comment><KeywordInComment>QUIET</KeywordInComment><Comment> is set to YES this implies that the</Comment><br/>
<Comment># messages are off.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>QUIET</Keyword><Normal Text>                  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>WARNINGS</KeywordInComment><Comment> tag can be used to turn on/off the warning messages that are</Comment><br/>
<Comment># generated to standard error (stderr) by doxygen. If </Comment><KeywordInComment>WARNINGS</KeywordInComment><Comment> is set to YES</Comment><br/>
<Comment># this implies that the </Comment><KeywordInComment>warnings</KeywordInComment><Comment> are on.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Tip: Turn </Comment><KeywordInComment>warnings</KeywordInComment><Comment> on while writing the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>WARNINGS</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>WARN_IF_UNDOCUMENTED</KeywordInComment><Comment> tag is set to YES then doxygen will generate</Comment><br/>
<Comment># </Comment><KeywordInComment>warnings</KeywordInComment><Comment> for undocumented members. If </Comment><KeywordInComment>EXTRACT_ALL</KeywordInComment><Comment> is set to YES then this flag</Comment><br/>
<Comment># will automatically be disabled.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>WARN_IF_UNDOCUMENTED</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>WARN_IF_DOC_ERROR</KeywordInComment><Comment> tag is set to YES, doxygen will generate </Comment><KeywordInComment>warnings</KeywordInComment><Comment> for</Comment><br/>
<Comment># potential errors in the documentation, such as not documenting some parameters</Comment><br/>
<Comment># in a documented function, or documenting parameters that don't exist or using</Comment><br/>
<Comment># markup commands wrongly.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>WARN_IF_DOC_ERROR</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># This </Comment><KeywordInComment>WARN_NO_PARAMDOC</KeywordInComment><Comment> option can be enabled to get </Comment><KeywordInComment>warnings</KeywordInComment><Comment> for functions that</Comment><br/>
<Comment># are documented, but have no documentation for their parameters or return</Comment><br/>
<Comment># value. If set to NO, doxygen will only warn about wrong or incomplete</Comment><br/>
<Comment># parameter documentation, but not about the absence of documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>WARN_NO_PARAMDOC</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>WARN_AS_ERROR</KeywordInComment><Comment> tag is set to YES then doxygen will immediately stop when</Comment><br/>
<Comment># a warning is encountered.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>WARN_AS_ERROR</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>WARN_FORMAT</KeywordInComment><Comment> tag determines the format of the warning messages that doxygen</Comment><br/>
<Comment># can produce. The string should contain the $file, $line, and $text tags, which</Comment><br/>
<Comment># will be replaced by the file and line number from which the warning originated</Comment><br/>
<Comment># and the warning text. Optionally the format may contain $version, which will</Comment><br/>
<Comment># be replaced by the version of the file (if it could be obtained via</Comment><br/>
<Comment># </Comment><KeywordInComment>FILE_VERSION_FILTER</KeywordInComment><Comment>)</Comment><br/>
<Comment># The default value is: $file:$line: $text.</Comment><br/>
<Error></Error><br/>
<Keyword>WARN_FORMAT</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> "$file:$line: $text"</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>WARN_LOGFILE</KeywordInComment><Comment> tag can be used to specify a file to which warning and error</Comment><br/>
<Comment># messages should be written. If left blank the output is written to standard</Comment><br/>
<Comment># error (stderr).</Comment><br/>
<Error></Error><br/>
<Keyword>WARN_LOGFILE</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the </Comment><KeywordInComment>input</KeywordInComment><Comment> files</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>INPUT</KeywordInComment><Comment> tag is used to specify the files and/or directories that contain</Comment><br/>
<Comment># documented source files. You may enter file names like myfile.cpp or</Comment><br/>
<Comment># directories like /usr/src/myproject. Separate the files or directories with</Comment><br/>
<Comment># spaces. See also </Comment><KeywordInComment>FILE_PATTERNS</KeywordInComment><Comment> and </Comment><KeywordInComment>EXTENSION_MAPPING</KeywordInComment><br/>
<Comment># Note: If this tag is empty the current directory is searched.</Comment><br/>
<Error></Error><br/>
<Keyword>INPUT</Keyword><Normal Text>                  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># This tag can be used to specify the character encoding of the source files</Comment><br/>
<Comment># that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses</Comment><br/>
<Comment># libiconv (or the iconv built into libc) for the transcoding. See the libiconv</Comment><br/>
<Comment># documentation (see: http://www.gnu.org/software/libiconv) for the list of</Comment><br/>
<Comment># possible encodings.</Comment><br/>
<Comment># The default value is: UTF-8.</Comment><br/>
<Error></Error><br/>
<Keyword>INPUT_ENCODING</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> UTF-8</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the value of the </Comment><KeywordInComment>INPUT</KeywordInComment><Comment> tag contains directories, you can use the</Comment><br/>
<Comment># </Comment><KeywordInComment>FILE_PATTERNS</KeywordInComment><Comment> tag to specify one or more wildcard patterns (like *.cpp and</Comment><br/>
<Comment># *.h) to filter out the source-files in the directories.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that for custom extensions or not directly supported extensions you also</Comment><br/>
<Comment># need to set </Comment><KeywordInComment>EXTENSION_MAPPING</KeywordInComment><Comment> for the extension otherwise the files are not</Comment><br/>
<Comment># read by doxygen.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># If left blank the following patterns are tested:*.c, *.cc, *.cxx, *.cpp,</Comment><br/>
<Comment># *.c++, *.java, *.ii, *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h,</Comment><br/>
<Comment># *.hh, *.hxx, *.hpp, *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc,</Comment><br/>
<Comment># *.m, *.markdown, *.md, *.mm, *.dox, *.py, *.pyw, *.f90, *.f, *.for, *.tcl,</Comment><br/>
<Comment># *.vhd, *.vhdl, *.ucf, *.qsf, *.as and *.js.</Comment><br/>
<Error></Error><br/>
<Keyword>FILE_PATTERNS</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>RECURSIVE</KeywordInComment><Comment> tag can be used to specify whether or not subdirectories should</Comment><br/>
<Comment># be searched for </Comment><KeywordInComment>input</KeywordInComment><Comment> files as well.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>RECURSIVE</Keyword><Normal Text>              </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>EXCLUDE</KeywordInComment><Comment> tag can be used to specify files and/or directories that should be</Comment><br/>
<Comment># excluded from the </Comment><KeywordInComment>INPUT</KeywordInComment><Comment> source files. This way you can easily </Comment><KeywordInComment>exclude</KeywordInComment><Comment> a</Comment><br/>
<Comment># subdirectory from a directory tree whose root is specified with the </Comment><KeywordInComment>INPUT</KeywordInComment><Comment> tag.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that relative paths are relative to the directory from which doxygen is</Comment><br/>
<Comment># run.</Comment><br/>
<Error></Error><br/>
<Keyword>EXCLUDE</Keyword><Normal Text>                </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>EXCLUDE_SYMLINKS</KeywordInComment><Comment> tag can be used to select whether or not files or</Comment><br/>
<Comment># directories that are symbolic links (a Unix file system feature) are excluded</Comment><br/>
<Comment># from the </Comment><KeywordInComment>input</KeywordInComment><Comment>.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXCLUDE_SYMLINKS</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the value of the </Comment><KeywordInComment>INPUT</KeywordInComment><Comment> tag contains directories, you can use the</Comment><br/>
<Comment># </Comment><KeywordInComment>EXCLUDE_PATTERNS</KeywordInComment><Comment> tag to specify one or more wildcard patterns to </Comment><KeywordInComment>exclude</KeywordInComment><br/>
<Comment># certain files from those directories.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that the wildcards are matched against the file with absolute path, so to</Comment><br/>
<Comment># </Comment><KeywordInComment>exclude</KeywordInComment><Comment> all test directories for example use the pattern */test/*</Comment><br/>
<Error></Error><br/>
<Keyword>EXCLUDE_PATTERNS</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>EXCLUDE_SYMBOLS</KeywordInComment><Comment> tag can be used to specify one or more symbol names</Comment><br/>
<Comment># (namespaces, classes, functions, etc.) that should be excluded from the</Comment><br/>
<Comment># output. The symbol name can be a fully qualified name, a word, or if the</Comment><br/>
<Comment># wildcard * is used, a substring. Examples: ANamespace, AClass,</Comment><br/>
<Comment># AClass::ANamespace, ANamespace::*Test</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that the wildcards are matched against the file with absolute path, so to</Comment><br/>
<Comment># </Comment><KeywordInComment>exclude</KeywordInComment><Comment> all test directories use the pattern */test/*</Comment><br/>
<Error></Error><br/>
<Keyword>EXCLUDE_SYMBOLS</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>EXAMPLE_PATH</KeywordInComment><Comment> tag can be used to specify one or more files or directories</Comment><br/>
<Comment># that contain example code fragments that are included (see the \include</Comment><br/>
<Comment># command).</Comment><br/>
<Error></Error><br/>
<Keyword>EXAMPLE_PATH</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the value of the </Comment><KeywordInComment>EXAMPLE_PATH</KeywordInComment><Comment> tag contains directories, you can use the</Comment><br/>
<Comment># </Comment><KeywordInComment>EXAMPLE_PATTERNS</KeywordInComment><Comment> tag to specify one or more wildcard pattern (like *.cpp and</Comment><br/>
<Comment># *.h) to filter out the source-files in the directories. If left blank all</Comment><br/>
<Comment># files are included.</Comment><br/>
<Error></Error><br/>
<Keyword>EXAMPLE_PATTERNS</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXAMPLE_RECURSIVE</KeywordInComment><Comment> tag is set to YES then subdirectories will be</Comment><br/>
<Comment># searched for </Comment><KeywordInComment>input</KeywordInComment><Comment> files to be used with the \include or \dontinclude commands</Comment><br/>
<Comment># irrespective of the value of the </Comment><KeywordInComment>RECURSIVE</KeywordInComment><Comment> tag.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>EXAMPLE_RECURSIVE</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>IMAGE_PATH</KeywordInComment><Comment> tag can be used to specify one or more files or directories</Comment><br/>
<Comment># that contain images that are to be included in the documentation (see the</Comment><br/>
<Comment># \image command).</Comment><br/>
<Error></Error><br/>
<Keyword>IMAGE_PATH</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>INPUT_FILTER</KeywordInComment><Comment> tag can be used to specify a program that doxygen should</Comment><br/>
<Comment># invoke to filter for each </Comment><KeywordInComment>input</KeywordInComment><Comment> file. Doxygen will invoke the filter program</Comment><br/>
<Comment># by executing (via popen()) the command:</Comment><br/>
<Comment>#</Comment><br/>
<Comment># <filter> <</Comment><KeywordInComment>input</KeywordInComment><Comment>-file></Comment><br/>
<Comment>#</Comment><br/>
<Comment># where <filter> is the value of the </Comment><KeywordInComment>INPUT_FILTER</KeywordInComment><Comment> tag, and <</Comment><KeywordInComment>input</KeywordInComment><Comment>-file> is the</Comment><br/>
<Comment># name of an </Comment><KeywordInComment>input</KeywordInComment><Comment> file. Doxygen will then use the output that the filter</Comment><br/>
<Comment># program writes to standard output. If </Comment><KeywordInComment>FILTER_PATTERNS</KeywordInComment><Comment> is specified, this tag</Comment><br/>
<Comment># will be ignored.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that the filter must not add or remove lines; it is applied before the</Comment><br/>
<Comment># code is scanned, but not when the output code is generated. If lines are added</Comment><br/>
<Comment># or removed, the anchors will not be placed correctly.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that for custom extensions or not directly supported extensions you also</Comment><br/>
<Comment># need to set </Comment><KeywordInComment>EXTENSION_MAPPING</KeywordInComment><Comment> for the extension otherwise the files are not</Comment><br/>
<Comment># properly processed by doxygen.</Comment><br/>
<Error></Error><br/>
<Keyword>INPUT_FILTER</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>FILTER_PATTERNS</KeywordInComment><Comment> tag can be used to specify filters on a per file pattern</Comment><br/>
<Comment># basis. Doxygen will compare the file name with each pattern and apply the</Comment><br/>
<Comment># filter if there is a match. The filters are a list of the form: pattern=filter</Comment><br/>
<Comment># (like *.cpp=my_cpp_filter). See </Comment><KeywordInComment>INPUT_FILTER</KeywordInComment><Comment> for further information on how</Comment><br/>
<Comment># filters are used. If the </Comment><KeywordInComment>FILTER_PATTERNS</KeywordInComment><Comment> tag is empty or if none of the</Comment><br/>
<Comment># patterns match the file name, </Comment><KeywordInComment>INPUT_FILTER</KeywordInComment><Comment> is applied.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that for custom extensions or not directly supported extensions you also</Comment><br/>
<Comment># need to set </Comment><KeywordInComment>EXTENSION_MAPPING</KeywordInComment><Comment> for the extension otherwise the files are not</Comment><br/>
<Comment># properly processed by doxygen.</Comment><br/>
<Error></Error><br/>
<Keyword>FILTER_PATTERNS</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>FILTER_SOURCE_FILES</KeywordInComment><Comment> tag is set to YES, the </Comment><KeywordInComment>input</KeywordInComment><Comment> filter (if set using</Comment><br/>
<Comment># </Comment><KeywordInComment>INPUT_FILTER</KeywordInComment><Comment>) will also be used to filter the </Comment><KeywordInComment>input</KeywordInComment><Comment> files that are used for</Comment><br/>
<Comment># producing the source files to browse (i.e. when </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment> is set to YES).</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>FILTER_SOURCE_FILES</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>FILTER_SOURCE_PATTERNS</KeywordInComment><Comment> tag can be used to specify source filters per file</Comment><br/>
<Comment># pattern. A pattern will override the setting for FILTER_PATTERN (if any) and</Comment><br/>
<Comment># it is also possible to disable source filtering for a specific pattern using</Comment><br/>
<Comment># *.ext= (so without naming a filter).</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>FILTER_SOURCE_FILES</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>FILTER_SOURCE_PATTERNS</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>USE_MDFILE_AS_MAINPAGE</KeywordInComment><Comment> tag refers to the name of a markdown file that</Comment><br/>
<Comment># is part of the </Comment><KeywordInComment>input</KeywordInComment><Comment>, its contents will be placed on the main page</Comment><br/>
<Comment># (index.html). This can be useful if you have a project on for instance GitHub</Comment><br/>
<Comment># and want to reuse the introduction page also for the doxygen output.</Comment><br/>
<Error></Error><br/>
<Keyword>USE_MDFILE_AS_MAINPAGE</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to source browsing</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment> tag is set to YES then a list of source files will be</Comment><br/>
<Comment># generated. Documented entities will be cross-referenced with these sources.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note: To get rid of all source code in the generated output, make sure that</Comment><br/>
<Comment># also </Comment><KeywordInComment>VERBATIM_HEADERS</KeywordInComment><Comment> is set to NO.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>SOURCE_BROWSER</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Setting the </Comment><KeywordInComment>INLINE_SOURCES</KeywordInComment><Comment> tag to YES will include the body of functions,</Comment><br/>
<Comment># classes and enums directly into the documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>INLINE_SOURCES</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Setting the </Comment><KeywordInComment>STRIP_CODE_COMMENTS</KeywordInComment><Comment> tag to YES will instruct doxygen to hide any</Comment><br/>
<Comment># special comment blocks from generated source code fragments. Normal C, C++ and</Comment><br/>
<Comment># Fortran comments will always remain visible.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>STRIP_CODE_COMMENTS</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>REFERENCED_BY_RELATION</KeywordInComment><Comment> tag is set to YES then for each documented</Comment><br/>
<Comment># function all documented functions referencing it will be listed.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>REFERENCED_BY_RELATION</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>REFERENCES_RELATION</KeywordInComment><Comment> tag is set to YES then for each documented function</Comment><br/>
<Comment># all documented entities called/used by that function will be listed.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>REFERENCES_RELATION</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>REFERENCES_LINK_SOURCE</KeywordInComment><Comment> tag is set to YES and </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment> tag is set</Comment><br/>
<Comment># to YES then the hyperlinks from functions in </Comment><KeywordInComment>REFERENCES_RELATION</KeywordInComment><Comment> and</Comment><br/>
<Comment># </Comment><KeywordInComment>REFERENCED_BY_RELATION</KeywordInComment><Comment> lists will link to the source code. Otherwise they will</Comment><br/>
<Comment># link to the documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>REFERENCES_LINK_SOURCE</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If </Comment><KeywordInComment>SOURCE_TOOLTIPS</KeywordInComment><Comment> is enabled (the default) then hovering a hyperlink in the</Comment><br/>
<Comment># source code will show a tooltip with additional information such as prototype,</Comment><br/>
<Comment># brief description and links to the definition and documentation. Since this</Comment><br/>
<Comment># will make the HTML file larger and loading of large files a bit slower, you</Comment><br/>
<Comment># can opt to disable this feature.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SOURCE_TOOLTIPS</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>USE_HTAGS</KeywordInComment><Comment> tag is set to YES then the references to source code will</Comment><br/>
<Comment># point to the HTML generated by the htags(1) tool instead of doxygen built-in</Comment><br/>
<Comment># source browser. The htags tool is part of GNU's global source tagging system</Comment><br/>
<Comment># (see http://www.gnu.org/software/global/global.html). You will need version</Comment><br/>
<Comment># 4.8.6 or higher.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># To use it do the following:</Comment><br/>
<Comment># - Install the latest version of global</Comment><br/>
<Comment># - Enable </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment> and </Comment><KeywordInComment>USE_HTAGS</KeywordInComment><Comment> in the config file</Comment><br/>
<Comment># - Make sure the </Comment><KeywordInComment>INPUT</KeywordInComment><Comment> points to the root of the source tree</Comment><br/>
<Comment># - Run doxygen as normal</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Doxygen will invoke htags (and that will in turn invoke gtags), so these</Comment><br/>
<Comment># tools must be available from the command line (i.e. in the search path).</Comment><br/>
<Comment>#</Comment><br/>
<Comment># The result: instead of the source browser generated by doxygen, the links to</Comment><br/>
<Comment># source code will now point to the output of htags.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>USE_HTAGS</Keyword><Normal Text>              </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>VERBATIM_HEADERS</KeywordInComment><Comment> tag is set the YES then doxygen will generate a</Comment><br/>
<Comment># verbatim copy of the header file for each class for which an include is</Comment><br/>
<Comment># specified. Set to NO to disable this.</Comment><br/>
<Comment># See also: Section \class.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>VERBATIM_HEADERS</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the alphabetical class index</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>ALPHABETICAL_INDEX</KeywordInComment><Comment> tag is set to YES, an alphabetical index of all</Comment><br/>
<Comment># compounds will be generated. Enable this if the project contains a lot of</Comment><br/>
<Comment># classes, structs, unions or interfaces.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>ALPHABETICAL_INDEX</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>COLS_IN_ALPHA_INDEX</KeywordInComment><Comment> tag can be used to specify the number of columns in</Comment><br/>
<Comment># which the alphabetical index list will be split.</Comment><br/>
<Comment># Minimum value: 1, maximum value: 20, default value: 5.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ALPHABETICAL_INDEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>COLS_IN_ALPHA_INDEX</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> 5</UntypedValue><br/>
<Error></Error><br/>
<Comment># In case all classes in a project start with a common prefix, all classes will</Comment><br/>
<Comment># be put under the same header in the alphabetical index. The </Comment><KeywordInComment>IGNORE_PREFIX</KeywordInComment><Comment> tag</Comment><br/>
<Comment># can be used to specify a prefix (or a list of prefixes) that should be ignored</Comment><br/>
<Comment># while generating the index headers.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ALPHABETICAL_INDEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>IGNORE_PREFIX</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the HTML output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> tag is set to YES, doxygen will generate HTML output</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_HTML</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_OUTPUT</KeywordInComment><Comment> tag is used to specify where the HTML docs will be put. If a</Comment><br/>
<Comment># relative path is entered the value of </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> will be put in front of</Comment><br/>
<Comment># it.</Comment><br/>
<Comment># The default directory is: html.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_OUTPUT</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> html</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_FILE_EXTENSION</KeywordInComment><Comment> tag can be used to specify the file extension for each</Comment><br/>
<Comment># generated HTML page (for example: .htm, .php, .asp).</Comment><br/>
<Comment># The default value is: .html.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_FILE_EXTENSION</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> .html</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_HEADER</KeywordInComment><Comment> tag can be used to specify a user-defined HTML header file for</Comment><br/>
<Comment># each generated HTML page. If the tag is left blank doxygen will generate a</Comment><br/>
<Comment># standard header.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># To get valid HTML the header file that includes any scripts and style sheets</Comment><br/>
<Comment># that doxygen needs, which is dependent on the configuration options used (e.g.</Comment><br/>
<Comment># the setting </Comment><KeywordInComment>GENERATE_TREEVIEW</KeywordInComment><Comment>). It is highly recommended to start with a</Comment><br/>
<Comment># default header using</Comment><br/>
<Comment># doxygen -w html new_header.html new_footer.html new_stylesheet.css</Comment><br/>
<Comment># YourConfigFile</Comment><br/>
<Comment># and then modify the file new_header.html. See also section "Doxygen usage"</Comment><br/>
<Comment># for information on how to generate the default header that doxygen normally</Comment><br/>
<Comment># uses.</Comment><br/>
<Comment># Note: The header is subject to change so you typically have to regenerate the</Comment><br/>
<Comment># default header when upgrading to a newer version of doxygen. For a description</Comment><br/>
<Comment># of the possible markers and block names see the documentation.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_HEADER</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_FOOTER</KeywordInComment><Comment> tag can be used to specify a user-defined HTML footer for each</Comment><br/>
<Comment># generated HTML page. If the tag is left blank doxygen will generate a standard</Comment><br/>
<Comment># footer. See </Comment><KeywordInComment>HTML_HEADER</KeywordInComment><Comment> for more information on how to generate a default</Comment><br/>
<Comment># footer and what special commands can be used inside the footer. See also</Comment><br/>
<Comment># section "Doxygen usage" for information on how to generate the default footer</Comment><br/>
<Comment># that doxygen normally uses.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_FOOTER</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_STYLESHEET</KeywordInComment><Comment> tag can be used to specify a user-defined cascading style</Comment><br/>
<Comment># sheet that is used by each HTML page. It can be used to fine-tune the look of</Comment><br/>
<Comment># the HTML output. If left blank doxygen will generate a default style sheet.</Comment><br/>
<Comment># See also section "Doxygen usage" for information on how to generate the style</Comment><br/>
<Comment># sheet that doxygen normally uses.</Comment><br/>
<Comment># Note: It is recommended to use </Comment><KeywordInComment>HTML_EXTRA_STYLESHEET</KeywordInComment><Comment> instead of this tag, as</Comment><br/>
<Comment># it is more robust and this tag (</Comment><KeywordInComment>HTML_STYLESHEET</KeywordInComment><Comment>) will in the future become</Comment><br/>
<Comment># obsolete.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_STYLESHEET</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_EXTRA_STYLESHEET</KeywordInComment><Comment> tag can be used to specify additional user-defined</Comment><br/>
<Comment># cascading style sheets that are included after the standard style sheets</Comment><br/>
<Comment># created by doxygen. Using this option one can overrule certain style aspects.</Comment><br/>
<Comment># This is preferred over using </Comment><KeywordInComment>HTML_STYLESHEET</KeywordInComment><Comment> since it does not replace the</Comment><br/>
<Comment># standard style sheet and is therefore more robust against future updates.</Comment><br/>
<Comment># Doxygen will copy the style sheet files to the output directory.</Comment><br/>
<Comment># Note: The order of the extra style sheet files is of importance (e.g. the last</Comment><br/>
<Comment># style sheet in the list overrules the setting of the previous ones in the</Comment><br/>
<Comment># list). For an example see the documentation.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_EXTRA_STYLESHEET</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_EXTRA_FILES</KeywordInComment><Comment> tag can be used to specify one or more extra images or</Comment><br/>
<Comment># other source files which should be copied to the HTML output directory. Note</Comment><br/>
<Comment># that these files will be copied to the base HTML output directory. Use the</Comment><br/>
<Comment># $relpath^ marker in the </Comment><KeywordInComment>HTML_HEADER</KeywordInComment><Comment> and/or </Comment><KeywordInComment>HTML_FOOTER</KeywordInComment><Comment> files to load these</Comment><br/>
<Comment># files. In the </Comment><KeywordInComment>HTML_STYLESHEET</KeywordInComment><Comment> file, use the file name only. Also note that the</Comment><br/>
<Comment># files will be copied as-is; there are no commands or markers available.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_EXTRA_FILES</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_COLORSTYLE_HUE</KeywordInComment><Comment> tag controls the color of the HTML output. Doxygen</Comment><br/>
<Comment># will adjust the colors in the style sheet and background images according to</Comment><br/>
<Comment># this color. Hue is specified as an angle on a colorwheel, see</Comment><br/>
<Comment># http://en.wikipedia.org/wiki/Hue for more information. For instance the value</Comment><br/>
<Comment># 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300</Comment><br/>
<Comment># purple, and 360 is red again.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 359, default value: 220.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_COLORSTYLE_HUE</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> 220</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_COLORSTYLE_SAT</KeywordInComment><Comment> tag controls the purity (or saturation) of the colors</Comment><br/>
<Comment># in the HTML output. For a value of 0 the output will use grayscales only. A</Comment><br/>
<Comment># value of 255 will produce the most vivid colors.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 255, default value: 100.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_COLORSTYLE_SAT</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> 100</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HTML_COLORSTYLE_GAMMA</KeywordInComment><Comment> tag controls the gamma correction applied to the</Comment><br/>
<Comment># luminance component of the colors in the HTML output. Values below 100</Comment><br/>
<Comment># gradually make the output lighter, whereas values above 100 make the output</Comment><br/>
<Comment># darker. The value divided by 100 is the actual gamma applied, so 80 represents</Comment><br/>
<Comment># a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not</Comment><br/>
<Comment># change the gamma.</Comment><br/>
<Comment># Minimum value: 40, maximum value: 240, default value: 80.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_COLORSTYLE_GAMMA</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> 80</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HTML_TIMESTAMP</KeywordInComment><Comment> tag is set to YES then the footer of each generated HTML</Comment><br/>
<Comment># page will contain the date and time when the page was generated. Setting this</Comment><br/>
<Comment># to YES can help to show when doxygen was last run and thus if the</Comment><br/>
<Comment># documentation is up to date.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_TIMESTAMP</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>HTML_DYNAMIC_SECTIONS</KeywordInComment><Comment> tag is set to YES then the generated HTML</Comment><br/>
<Comment># documentation will contain sections that can be hidden and shown after the</Comment><br/>
<Comment># page has loaded.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_DYNAMIC_SECTIONS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># With </Comment><KeywordInComment>HTML_INDEX_NUM_ENTRIES</KeywordInComment><Comment> one can control the preferred number of entries</Comment><br/>
<Comment># shown in the various tree structured indices initially; the user can expand</Comment><br/>
<Comment># and collapse entries dynamically later on. Doxygen will expand the tree to</Comment><br/>
<Comment># such a level that at most the specified number of entries are visible (unless</Comment><br/>
<Comment># a fully collapsed tree already exceeds this amount). So setting the number of</Comment><br/>
<Comment># entries 1 will produce a full collapsed tree by default. 0 is a special value</Comment><br/>
<Comment># representing an infinite number of entries and will result in a full expanded</Comment><br/>
<Comment># tree by default.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 9999, default value: 100.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HTML_INDEX_NUM_ENTRIES</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> 100</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_DOCSET</KeywordInComment><Comment> tag is set to YES, additional index files will be</Comment><br/>
<Comment># generated that can be used as </Comment><KeywordInComment>input</KeywordInComment><Comment> for Apple's Xcode 3 integrated development</Comment><br/>
<Comment># environment (see: http://developer.apple.com/tools/xcode/), introduced with</Comment><br/>
<Comment># OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a</Comment><br/>
<Comment># Makefile in the HTML output directory. Running make will produce the docset in</Comment><br/>
<Comment># that directory and running make install will install the docset in</Comment><br/>
<Comment># ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at</Comment><br/>
<Comment># startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html</Comment><br/>
<Comment># for more information.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_DOCSET</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># This tag determines the name of the docset feed. A documentation feed provides</Comment><br/>
<Comment># an umbrella under which multiple documentation sets from a single provider</Comment><br/>
<Comment># (such as a company or product suite) can be grouped.</Comment><br/>
<Comment># The default value is: Doxygen generated docs.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_DOCSET</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOCSET_FEEDNAME</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> "Doxygen generated docs"</UntypedValue><br/>
<Error></Error><br/>
<Comment># This tag specifies a string that should uniquely identify the documentation</Comment><br/>
<Comment># set bundle. This should be a reverse domain-name style string, e.g.</Comment><br/>
<Comment># com.mycompany.MyDocSet. Doxygen will append .docset to the name.</Comment><br/>
<Comment># The default value is: org.doxygen.Project.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_DOCSET</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOCSET_BUNDLE_ID</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> org.doxygen.Project</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOCSET_PUBLISHER_ID</KeywordInComment><Comment> tag specifies a string that should uniquely identify</Comment><br/>
<Comment># the documentation publisher. This should be a reverse domain-name style</Comment><br/>
<Comment># string, e.g. com.mycompany.MyDocSet.documentation.</Comment><br/>
<Comment># The default value is: org.doxygen.Publisher.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_DOCSET</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOCSET_PUBLISHER_ID</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> org.doxygen.Publisher</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOCSET_PUBLISHER_NAME</KeywordInComment><Comment> tag identifies the documentation publisher.</Comment><br/>
<Comment># The default value is: Publisher.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_DOCSET</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOCSET_PUBLISHER_NAME</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><UntypedValue> Publisher</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> tag is set to YES then doxygen generates three</Comment><br/>
<Comment># additional HTML index files: index.hhp, index.hhc, and index.hhk. The</Comment><br/>
<Comment># index.hhp is a project file that can be read by Microsoft's HTML Help Workshop</Comment><br/>
<Comment># (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on</Comment><br/>
<Comment># Windows.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># The HTML Help Workshop contains a compiler that can convert all HTML output</Comment><br/>
<Comment># generated by doxygen into a single compiled HTML file (.chm). Compiled HTML</Comment><br/>
<Comment># files are now used as the Windows 98 help format, and will replace the old</Comment><br/>
<Comment># Windows help format (.hlp) on all Windows platforms in the future. Compressed</Comment><br/>
<Comment># HTML files also contain an index, a table of contents, and you can search for</Comment><br/>
<Comment># words in the documentation. The HTML workshop also contains a viewer for</Comment><br/>
<Comment># compressed HTML files.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_HTMLHELP</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>CHM_FILE</KeywordInComment><Comment> tag can be used to specify the file name of the resulting .chm</Comment><br/>
<Comment># file. You can add a path in front of the file if the result should not be</Comment><br/>
<Comment># written to the html output directory.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>CHM_FILE</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>HHC_LOCATION</KeywordInComment><Comment> tag can be used to specify the location (absolute path</Comment><br/>
<Comment># including file name) of the HTML help compiler (hhc.exe). If non-empty,</Comment><br/>
<Comment># doxygen will try to run the HTML help compiler on the generated index.hhp.</Comment><br/>
<Comment># The file has to be specified with full path.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HHC_LOCATION</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>GENERATE_CHI</KeywordInComment><Comment> flag controls if a separate .chi index file is generated</Comment><br/>
<Comment># (YES) or that it should be included in the master .chm file (NO).</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_CHI</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>CHM_INDEX_ENCODING</KeywordInComment><Comment> is used to encode HtmlHelp index (hhk), content (hhc)</Comment><br/>
<Comment># and project file content.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>CHM_INDEX_ENCODING</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>BINARY_TOC</KeywordInComment><Comment> flag controls whether a binary table of contents is generated</Comment><br/>
<Comment># (YES) or a normal table of contents (NO) in the .chm file. Furthermore it</Comment><br/>
<Comment># enables the Previous and Next buttons.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>BINARY_TOC</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>TOC_EXPAND</KeywordInComment><Comment> flag can be set to YES to add extra items for group members to</Comment><br/>
<Comment># the table of contents of the HTML help documentation and to the tree view.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>TOC_EXPAND</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> tag is set to YES and both </Comment><KeywordInComment>QHP_NAMESPACE</KeywordInComment><Comment> and</Comment><br/>
<Comment># </Comment><KeywordInComment>QHP_VIRTUAL_FOLDER</KeywordInComment><Comment> are set, an additional index file will be generated that</Comment><br/>
<Comment># can be used as </Comment><KeywordInComment>input</KeywordInComment><Comment> for Qt's qhelpgenerator to generate a Qt Compressed Help</Comment><br/>
<Comment># (.qch) of the generated HTML documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_QHP</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>QHG_LOCATION</KeywordInComment><Comment> tag is specified, the </Comment><KeywordInComment>QCH_FILE</KeywordInComment><Comment> tag can be used to specify</Comment><br/>
<Comment># the file name of the resulting .qch file. The path specified is relative to</Comment><br/>
<Comment># the HTML output folder.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QCH_FILE</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>QHP_NAMESPACE</KeywordInComment><Comment> tag specifies the namespace to use when generating Qt Help</Comment><br/>
<Comment># Project output. For more information please see Qt Help Project / Namespace</Comment><br/>
<Comment># (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).</Comment><br/>
<Comment># The default value is: org.doxygen.Project.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QHP_NAMESPACE</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> org.doxygen.Project</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>QHP_VIRTUAL_FOLDER</KeywordInComment><Comment> tag specifies the namespace to use when generating Qt</Comment><br/>
<Comment># Help Project output. For more information please see Qt Help Project / Virtual</Comment><br/>
<Comment># Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-</Comment><br/>
<Comment># folders).</Comment><br/>
<Comment># The default value is: doc.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QHP_VIRTUAL_FOLDER</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> doc</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>QHP_CUST_FILTER_NAME</KeywordInComment><Comment> tag is set, it specifies the name of a custom</Comment><br/>
<Comment># filter to add. For more information please see Qt Help Project / Custom</Comment><br/>
<Comment># Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-</Comment><br/>
<Comment># filters).</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QHP_CUST_FILTER_NAME</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>QHP_CUST_FILTER_ATTRS</KeywordInComment><Comment> tag specifies the list of the attributes of the</Comment><br/>
<Comment># custom filter to add. For more information please see Qt Help Project / Custom</Comment><br/>
<Comment># Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-</Comment><br/>
<Comment># filters).</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QHP_CUST_FILTER_ATTRS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>QHP_SECT_FILTER_ATTRS</KeywordInComment><Comment> tag specifies the list of the attributes this</Comment><br/>
<Comment># project's filter section matches. Qt Help Project / Filter Attributes (see:</Comment><br/>
<Comment># http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QHP_SECT_FILTER_ATTRS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>QHG_LOCATION</KeywordInComment><Comment> tag can be used to specify the location of Qt's</Comment><br/>
<Comment># qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the</Comment><br/>
<Comment># generated .qhp file.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>QHG_LOCATION</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_ECLIPSEHELP</KeywordInComment><Comment> tag is set to YES, additional index files will be</Comment><br/>
<Comment># generated, together with the HTML files, they form an Eclipse help plugin. To</Comment><br/>
<Comment># install this plugin and make it available under the help contents menu in</Comment><br/>
<Comment># Eclipse, the contents of the directory containing the HTML and XML files needs</Comment><br/>
<Comment># to be copied into the plugins directory of eclipse. The name of the directory</Comment><br/>
<Comment># within the plugins directory should be the same as the </Comment><KeywordInComment>ECLIPSE_DOC_ID</KeywordInComment><Comment> value.</Comment><br/>
<Comment># After copying Eclipse needs to be restarted before the help appears.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_ECLIPSEHELP</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># A unique identifier for the Eclipse help plugin. When installing the plugin</Comment><br/>
<Comment># the directory name containing the HTML and XML files should also have this</Comment><br/>
<Comment># name. Each documentation set should have its own identifier.</Comment><br/>
<Comment># The default value is: org.doxygen.Project.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_ECLIPSEHELP</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>ECLIPSE_DOC_ID</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> org.doxygen.Project</UntypedValue><br/>
<Error></Error><br/>
<Comment># If you want full control over the layout of the generated HTML pages it might</Comment><br/>
<Comment># be necessary to disable the index and replace it with your own. The</Comment><br/>
<Comment># </Comment><KeywordInComment>DISABLE_INDEX</KeywordInComment><Comment> tag can be used to turn on/off the condensed index (tabs) at top</Comment><br/>
<Comment># of each HTML page. A value of NO enables the index and the value YES disables</Comment><br/>
<Comment># it. Since the tabs in the index contain the same information as the navigation</Comment><br/>
<Comment># tree, you can set this option to YES if you also set </Comment><KeywordInComment>GENERATE_TREEVIEW</KeywordInComment><Comment> to YES.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DISABLE_INDEX</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>GENERATE_TREEVIEW</KeywordInComment><Comment> tag is used to specify whether a tree-like index</Comment><br/>
<Comment># structure should be generated to display hierarchical information. If the tag</Comment><br/>
<Comment># value is set to YES, a side panel will be generated containing a tree-like</Comment><br/>
<Comment># index structure (just like the one that is generated for HTML Help). For this</Comment><br/>
<Comment># to work a browser that supports JavaScript, DHTML, CSS and frames is required</Comment><br/>
<Comment># (i.e. any modern browser). Windows users are probably better off using the</Comment><br/>
<Comment># HTML help feature. Via custom style sheets (see </Comment><KeywordInComment>HTML_EXTRA_STYLESHEET</KeywordInComment><Comment>) one can</Comment><br/>
<Comment># further fine-tune the look of the index. As an example, the default style</Comment><br/>
<Comment># sheet generated by doxygen has an example that shows how to put an image at</Comment><br/>
<Comment># the root of the tree instead of the </Comment><KeywordInComment>PROJECT_NAME</KeywordInComment><Comment>. Since the tree basically has</Comment><br/>
<Comment># the same information as the tab index, you could consider setting</Comment><br/>
<Comment># </Comment><KeywordInComment>DISABLE_INDEX</KeywordInComment><Comment> to YES when enabling this option.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_TREEVIEW</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>ENUM_VALUES_PER_LINE</KeywordInComment><Comment> tag can be used to set the number of enum values that</Comment><br/>
<Comment># doxygen will group on one line in the generated HTML documentation.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that a value of 0 will completely suppress the enum values from appearing</Comment><br/>
<Comment># in the overview section.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 20, default value: 4.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>ENUM_VALUES_PER_LINE</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> 4</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the treeview is enabled (see </Comment><KeywordInComment>GENERATE_TREEVIEW</KeywordInComment><Comment>) then this tag can be used</Comment><br/>
<Comment># to set the initial width (in pixels) of the frame in which the tree is shown.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 1500, default value: 250.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>TREEVIEW_WIDTH</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> 250</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXT_LINKS_IN_WINDOW</KeywordInComment><Comment> option is set to YES, doxygen will open links to</Comment><br/>
<Comment># external symbols imported via tag files in a separate window.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXT_LINKS_IN_WINDOW</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Use this tag to change the font size of LaTeX formulas included as images in</Comment><br/>
<Comment># the HTML documentation. When you change the font size after a successful</Comment><br/>
<Comment># doxygen run you need to manually remove any form_*.png images from the HTML</Comment><br/>
<Comment># output directory to force them to be regenerated.</Comment><br/>
<Comment># Minimum value: 8, maximum value: 50, default value: 10.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>FORMULA_FONTSIZE</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> 10</UntypedValue><br/>
<Error></Error><br/>
<Comment># Use the FORMULA_TRANPARENT tag to determine whether or not the images</Comment><br/>
<Comment># generated for formulas are transparent PNGs. Transparent PNGs are not</Comment><br/>
<Comment># supported properly for IE 6.0, but are supported on all modern browsers.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that when changing this option you need to delete any form_*.png files in</Comment><br/>
<Comment># the HTML output directory before the changes have effect.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>FORMULA_TRANSPARENT</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># Enable the </Comment><KeywordInComment>USE_MATHJAX</KeywordInComment><Comment> option to render LaTeX formulas using MathJax (see</Comment><br/>
<Comment># http://www.mathjax.org) which uses client side Javascript for the rendering</Comment><br/>
<Comment># instead of using pre-rendered bitmaps. Use this if you do not have LaTeX</Comment><br/>
<Comment># installed or if you want to formulas look prettier in the HTML output. When</Comment><br/>
<Comment># enabled you may also need to install MathJax separately and configure the path</Comment><br/>
<Comment># to it using the </Comment><KeywordInComment>MATHJAX_RELPATH</KeywordInComment><Comment> option.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>USE_MATHJAX</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># When MathJax is enabled you can set the default output format to be used for</Comment><br/>
<Comment># the MathJax output. See the MathJax site (see:</Comment><br/>
<Comment># http://docs.mathjax.org/en/latest/output.html) for more details.</Comment><br/>
<Comment># Possible values are: HTML-CSS (which is slower, but has the best</Comment><br/>
<Comment># compatibility), NativeMML (i.e. MathML) and SVG.</Comment><br/>
<Comment># The default value is: HTML-CSS.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>USE_MATHJAX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MATHJAX_FORMAT</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> HTML-CSS</UntypedValue><br/>
<Error></Error><br/>
<Comment># When MathJax is enabled you need to specify the location relative to the HTML</Comment><br/>
<Comment># output directory using the </Comment><KeywordInComment>MATHJAX_RELPATH</KeywordInComment><Comment> option. The destination directory</Comment><br/>
<Comment># should contain the MathJax.js script. For instance, if the mathjax directory</Comment><br/>
<Comment># is located at the same level as the HTML output directory, then</Comment><br/>
<Comment># </Comment><KeywordInComment>MATHJAX_RELPATH</KeywordInComment><Comment> should be ../mathjax. The default value points to the MathJax</Comment><br/>
<Comment># Content Delivery Network so you can quickly see the result without installing</Comment><br/>
<Comment># MathJax. However, it is strongly recommended to install a local copy of</Comment><br/>
<Comment># MathJax from http://www.mathjax.org before deployment.</Comment><br/>
<Comment># The default value is: http://cdn.mathjax.org/mathjax/latest.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>USE_MATHJAX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MATHJAX_RELPATH</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> http://cdn.mathjax.org/mathjax/latest</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MATHJAX_EXTENSIONS</KeywordInComment><Comment> tag can be used to specify one or more MathJax</Comment><br/>
<Comment># extension names that should be enabled during MathJax rendering. For example</Comment><br/>
<Comment># </Comment><KeywordInComment>MATHJAX_EXTENSIONS</KeywordInComment><Comment> = TeX/AMSmath TeX/AMSsymbols</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>USE_MATHJAX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MATHJAX_EXTENSIONS</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MATHJAX_CODEFILE</KeywordInComment><Comment> tag can be used to specify a file with javascript pieces</Comment><br/>
<Comment># of code that will be used on startup of the MathJax code. See the MathJax site</Comment><br/>
<Comment># (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an</Comment><br/>
<Comment># example see the documentation.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>USE_MATHJAX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MATHJAX_CODEFILE</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># When the </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> tag is enabled doxygen will generate a search box for</Comment><br/>
<Comment># the HTML output. The underlying search engine uses javascript and DHTML and</Comment><br/>
<Comment># should work on any modern browser. Note that when using HTML help</Comment><br/>
<Comment># (</Comment><KeywordInComment>GENERATE_HTMLHELP</KeywordInComment><Comment>), Qt help (</Comment><KeywordInComment>GENERATE_QHP</KeywordInComment><Comment>), or docsets (</Comment><KeywordInComment>GENERATE_DOCSET</KeywordInComment><Comment>)</Comment><br/>
<Comment># there is already a search function so this one should typically be disabled.</Comment><br/>
<Comment># For large projects the javascript based search engine can be slow, then</Comment><br/>
<Comment># enabling </Comment><KeywordInComment>SERVER_BASED_SEARCH</KeywordInComment><Comment> may provide a better solution. It is possible to</Comment><br/>
<Comment># search using the keyboard; to jump to the search box use <access key> + S</Comment><br/>
<Comment># (what the <access key> is depends on the OS and browser, but it is typically</Comment><br/>
<Comment># <CTRL>, <ALT>/<option>, or both). Inside the search box use the <cursor down</Comment><br/>
<Comment># key> to jump into the search results window, the results can be navigated</Comment><br/>
<Comment># using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel</Comment><br/>
<Comment># the search. The filter options can be selected when the cursor is inside the</Comment><br/>
<Comment># search box by pressing <Shift>+<cursor down>. Also here use the <cursor keys></Comment><br/>
<Comment># to select a filter and <Enter> or <escape> to activate or cancel the filter</Comment><br/>
<Comment># option.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_HTML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SEARCHENGINE</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># When the </Comment><KeywordInComment>SERVER_BASED_SEARCH</KeywordInComment><Comment> tag is enabled the search engine will be</Comment><br/>
<Comment># implemented using a web server instead of a web client using Javascript. There</Comment><br/>
<Comment># are two flavors of web server based searching depending on the </Comment><KeywordInComment>EXTERNAL_SEARCH</KeywordInComment><br/>
<Comment># setting. When disabled, doxygen will generate a PHP script for searching and</Comment><br/>
<Comment># an index file used by the script. When </Comment><KeywordInComment>EXTERNAL_SEARCH</KeywordInComment><Comment> is enabled the indexing</Comment><br/>
<Comment># and searching needs to be provided by external tools. See the section</Comment><br/>
<Comment># "External Indexing and Searching" for details.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SERVER_BASED_SEARCH</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># When </Comment><KeywordInComment>EXTERNAL_SEARCH</KeywordInComment><Comment> tag is enabled doxygen will no longer generate the PHP</Comment><br/>
<Comment># script for searching. Instead the search results are written to an XML file</Comment><br/>
<Comment># which needs to be processed by an external indexer. Doxygen will invoke an</Comment><br/>
<Comment># external search engine pointed to by the </Comment><KeywordInComment>SEARCHENGINE_URL</KeywordInComment><Comment> option to obtain the</Comment><br/>
<Comment># search results.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Doxygen ships with an example indexer (doxyindexer) and search engine</Comment><br/>
<Comment># (doxysearch.cgi) which are based on the open source search engine library</Comment><br/>
<Comment># Xapian (see: http://xapian.org/).</Comment><br/>
<Comment>#</Comment><br/>
<Comment># See the section "External Indexing and Searching" for details.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTERNAL_SEARCH</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>SEARCHENGINE_URL</KeywordInComment><Comment> should point to a search engine hosted by a web server</Comment><br/>
<Comment># which will return the search results when </Comment><KeywordInComment>EXTERNAL_SEARCH</KeywordInComment><Comment> is enabled.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Doxygen ships with an example indexer (doxyindexer) and search engine</Comment><br/>
<Comment># (doxysearch.cgi) which are based on the open source search engine library</Comment><br/>
<Comment># Xapian (see: http://xapian.org/). See the section "External Indexing and</Comment><br/>
<Comment># Searching" for details.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SEARCHENGINE_URL</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># When </Comment><KeywordInComment>SERVER_BASED_SEARCH</KeywordInComment><Comment> and </Comment><KeywordInComment>EXTERNAL_SEARCH</KeywordInComment><Comment> are both enabled the unindexed</Comment><br/>
<Comment># search data is written to a file for indexing by an external tool. With the</Comment><br/>
<Comment># </Comment><KeywordInComment>SEARCHDATA_FILE</KeywordInComment><Comment> tag the name of this file can be specified.</Comment><br/>
<Comment># The default file is: searchdata.xml.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SEARCHDATA_FILE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> searchdata.xml</UntypedValue><br/>
<Error></Error><br/>
<Comment># When </Comment><KeywordInComment>SERVER_BASED_SEARCH</KeywordInComment><Comment> and </Comment><KeywordInComment>EXTERNAL_SEARCH</KeywordInComment><Comment> are both enabled the</Comment><br/>
<Comment># </Comment><KeywordInComment>EXTERNAL_SEARCH_ID</KeywordInComment><Comment> tag can be used as an identifier for the project. This is</Comment><br/>
<Comment># useful in combination with </Comment><KeywordInComment>EXTRA_SEARCH_MAPPINGS</KeywordInComment><Comment> to search through multiple</Comment><br/>
<Comment># projects and redirect the results back to the right project.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTERNAL_SEARCH_ID</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>EXTRA_SEARCH_MAPPINGS</KeywordInComment><Comment> tag can be used to enable searching through doxygen</Comment><br/>
<Comment># projects other than the one defined by this configuration file, but that are</Comment><br/>
<Comment># all added to the same external search index. Each project needs to have a</Comment><br/>
<Comment># unique id set via </Comment><KeywordInComment>EXTERNAL_SEARCH_ID</KeywordInComment><Comment>. The search mapping then maps the id of</Comment><br/>
<Comment># to a relative location where the documentation can be found. The format is:</Comment><br/>
<Comment># </Comment><KeywordInComment>EXTRA_SEARCH_MAPPINGS</KeywordInComment><Comment> = tagname1=loc1 tagname2=loc2 ...</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCHENGINE</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRA_SEARCH_MAPPINGS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the LaTeX output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> tag is set to YES, doxygen will generate LaTeX output.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_LATEX</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_OUTPUT</KeywordInComment><Comment> tag is used to specify where the LaTeX docs will be put. If a</Comment><br/>
<Comment># relative path is entered the value of </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> will be put in front of</Comment><br/>
<Comment># it.</Comment><br/>
<Comment># The default directory is: latex.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_OUTPUT</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> latex</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_CMD_NAME</KeywordInComment><Comment> tag can be used to specify the LaTeX command name to be</Comment><br/>
<Comment># invoked.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that when enabling </Comment><KeywordInComment>USE_PDFLATEX</KeywordInComment><Comment> this option is only used for generating</Comment><br/>
<Comment># bitmaps for formulas in the HTML output, but not in the Makefile that is</Comment><br/>
<Comment># written to the output directory.</Comment><br/>
<Comment># The default file is: latex.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_CMD_NAME</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> latex</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MAKEINDEX_CMD_NAME</KeywordInComment><Comment> tag can be used to specify the command name to generate</Comment><br/>
<Comment># index for LaTeX.</Comment><br/>
<Comment># The default file is: makeindex.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MAKEINDEX_CMD_NAME</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> makeindex</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>COMPACT_LATEX</KeywordInComment><Comment> tag is set to YES, doxygen generates more compact LaTeX</Comment><br/>
<Comment># documents. This may be useful for small projects and may help to save some</Comment><br/>
<Comment># trees in general.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>COMPACT_LATEX</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>PAPER_TYPE</KeywordInComment><Comment> tag can be used to set the paper type that is used by the</Comment><br/>
<Comment># printer.</Comment><br/>
<Comment># Possible values are: a4 (210 x 297 mm), letter (8.5 x 11 inches), legal (8.5 x</Comment><br/>
<Comment># 14 inches) and executive (7.25 x 10.5 inches).</Comment><br/>
<Comment># The default value is: a4.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>PAPER_TYPE</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> a4</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>EXTRA_PACKAGES</KeywordInComment><Comment> tag can be used to specify one or more LaTeX package names</Comment><br/>
<Comment># that should be included in the LaTeX output. The package can be specified just</Comment><br/>
<Comment># by its name or with the correct syntax as to be used with the LaTeX</Comment><br/>
<Comment># \usepackage command. To get the times font for instance you can specify :</Comment><br/>
<Comment># </Comment><KeywordInComment>EXTRA_PACKAGES</KeywordInComment><Comment>=times or </Comment><KeywordInComment>EXTRA_PACKAGES</KeywordInComment><Comment>={times}</Comment><br/>
<Comment># To use the option intlimits with the amsmath package you can specify:</Comment><br/>
<Comment># </Comment><KeywordInComment>EXTRA_PACKAGES</KeywordInComment><Comment>=[intlimits]{amsmath}</Comment><br/>
<Comment># If left blank no extra packages will be included.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTRA_PACKAGES</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_HEADER</KeywordInComment><Comment> tag can be used to specify a personal LaTeX header for the</Comment><br/>
<Comment># generated LaTeX document. The header should contain everything until the first</Comment><br/>
<Comment># chapter. If it is left blank doxygen will generate a standard header. See</Comment><br/>
<Comment># section "Doxygen usage" for information on how to let doxygen write the</Comment><br/>
<Comment># default header to a separate file.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note: Only use a user-defined header if you know what you are doing! The</Comment><br/>
<Comment># following commands have a special meaning inside the header: $title,</Comment><br/>
<Comment># $datetime, $date, $doxygenversion, $projectname, $projectnumber,</Comment><br/>
<Comment># $projectbrief, $projectlogo. Doxygen will replace $title with the empty</Comment><br/>
<Comment># string, for the replacement values of the other commands the user is referred</Comment><br/>
<Comment># to </Comment><KeywordInComment>HTML_HEADER</KeywordInComment><Comment>.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_HEADER</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_FOOTER</KeywordInComment><Comment> tag can be used to specify a personal LaTeX footer for the</Comment><br/>
<Comment># generated LaTeX document. The footer should contain everything after the last</Comment><br/>
<Comment># chapter. If it is left blank doxygen will generate a standard footer. See</Comment><br/>
<Comment># </Comment><KeywordInComment>LATEX_HEADER</KeywordInComment><Comment> for more information on how to generate a default footer and what</Comment><br/>
<Comment># special commands can be used inside the footer.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note: Only use a user-defined footer if you know what you are doing!</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_FOOTER</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_EXTRA_STYLESHEET</KeywordInComment><Comment> tag can be used to specify additional user-defined</Comment><br/>
<Comment># LaTeX style sheets that are included after the standard style sheets created</Comment><br/>
<Comment># by doxygen. Using this option one can overrule certain style aspects. Doxygen</Comment><br/>
<Comment># will copy the style sheet files to the output directory.</Comment><br/>
<Comment># Note: The order of the extra style sheet files is of importance (e.g. the last</Comment><br/>
<Comment># style sheet in the list overrules the setting of the previous ones in the</Comment><br/>
<Comment># list).</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_EXTRA_STYLESHEET</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_EXTRA_FILES</KeywordInComment><Comment> tag can be used to specify one or more extra images or</Comment><br/>
<Comment># other source files which should be copied to the </Comment><KeywordInComment>LATEX_OUTPUT</KeywordInComment><Comment> output</Comment><br/>
<Comment># directory. Note that the files will be copied as-is; there are no commands or</Comment><br/>
<Comment># markers available.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_EXTRA_FILES</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>PDF_HYPERLINKS</KeywordInComment><Comment> tag is set to YES, the LaTeX that is generated is</Comment><br/>
<Comment># prepared for conversion to PDF (using ps2pdf or pdflatex). The PDF file will</Comment><br/>
<Comment># contain links (just like the HTML output) instead of page references. This</Comment><br/>
<Comment># makes the output suitable for online browsing using a PDF viewer.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>PDF_HYPERLINKS</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>USE_PDFLATEX</KeywordInComment><Comment> tag is set to YES, doxygen will use pdflatex to generate</Comment><br/>
<Comment># the PDF file directly from the LaTeX files. Set this option to YES, to get a</Comment><br/>
<Comment># higher quality PDF documentation.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>USE_PDFLATEX</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>LATEX_BATCHMODE</KeywordInComment><Comment> tag is set to YES, doxygen will add the \batchmode</Comment><br/>
<Comment># command to the generated LaTeX files. This will instruct LaTeX to keep running</Comment><br/>
<Comment># if errors occur, instead of asking the user for help. This option is also used</Comment><br/>
<Comment># when generating formulas in HTML.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_BATCHMODE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>LATEX_HIDE_INDICES</KeywordInComment><Comment> tag is set to YES then doxygen will not include the</Comment><br/>
<Comment># index chapters (such as File Index, Compound Index, etc.) in the output.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_HIDE_INDICES</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>LATEX_SOURCE_CODE</KeywordInComment><Comment> tag is set to YES then doxygen will include source</Comment><br/>
<Comment># code with syntax highlighting in the LaTeX output.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that which sources are shown also depends on other settings such as</Comment><br/>
<Comment># </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment>.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_SOURCE_CODE</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>LATEX_BIB_STYLE</KeywordInComment><Comment> tag can be used to specify the style to use for the</Comment><br/>
<Comment># bibliography, e.g. plainnat, or ieeetr. See</Comment><br/>
<Comment># http://en.wikipedia.org/wiki/BibTeX and \cite for more info.</Comment><br/>
<Comment># The default value is: plain.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_BIB_STYLE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> plain</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>LATEX_TIMESTAMP</KeywordInComment><Comment> tag is set to YES then the footer of each generated</Comment><br/>
<Comment># page will contain the date and time when the page was generated. Setting this</Comment><br/>
<Comment># to NO can help when comparing the output of multiple runs.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_LATEX</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>LATEX_TIMESTAMP</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the RTF output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> tag is set to YES, doxygen will generate RTF output. The</Comment><br/>
<Comment># RTF output is optimized for Word 97 and may not look too pretty with other RTF</Comment><br/>
<Comment># readers/editors.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_RTF</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>RTF_OUTPUT</KeywordInComment><Comment> tag is used to specify where the RTF docs will be put. If a</Comment><br/>
<Comment># relative path is entered the value of </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> will be put in front of</Comment><br/>
<Comment># it.</Comment><br/>
<Comment># The default directory is: rtf.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>RTF_OUTPUT</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> rtf</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>COMPACT_RTF</KeywordInComment><Comment> tag is set to YES, doxygen generates more compact RTF</Comment><br/>
<Comment># documents. This may be useful for small projects and may help to save some</Comment><br/>
<Comment># trees in general.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>COMPACT_RTF</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>RTF_HYPERLINKS</KeywordInComment><Comment> tag is set to YES, the RTF that is generated will</Comment><br/>
<Comment># contain hyperlink fields. The RTF file will contain links (just like the HTML</Comment><br/>
<Comment># output) instead of page references. This makes the output suitable for online</Comment><br/>
<Comment># browsing using Word or some other Word compatible readers that support those</Comment><br/>
<Comment># fields.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note: WordPad (write) and others do not support links.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>RTF_HYPERLINKS</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Load stylesheet definitions from file. Syntax is similar to doxygen's config</Comment><br/>
<Comment># file, i.e. a series of assignments. You only have to provide replacements,</Comment><br/>
<Comment># missing definitions are set to their default value.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># See also section "Doxygen usage" for information on how to generate the</Comment><br/>
<Comment># default style sheet that doxygen normally uses.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>RTF_STYLESHEET_FILE</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># Set optional variables used in the generation of an RTF document. Syntax is</Comment><br/>
<Comment># similar to doxygen's config file. A template extensions file can be generated</Comment><br/>
<Comment># using doxygen -e rtf extensionFile.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>RTF_EXTENSIONS_FILE</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>RTF_SOURCE_CODE</KeywordInComment><Comment> tag is set to YES then doxygen will include source code</Comment><br/>
<Comment># with syntax highlighting in the RTF output.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that which sources are shown also depends on other settings such as</Comment><br/>
<Comment># </Comment><KeywordInComment>SOURCE_BROWSER</KeywordInComment><Comment>.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_RTF</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>RTF_SOURCE_CODE</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the man page output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_MAN</KeywordInComment><Comment> tag is set to YES, doxygen will generate man pages for</Comment><br/>
<Comment># classes and files.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_MAN</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MAN_OUTPUT</KeywordInComment><Comment> tag is used to specify where the man pages will be put. If a</Comment><br/>
<Comment># relative path is entered the value of </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> will be put in front of</Comment><br/>
<Comment># it. A directory man3 will be created inside the directory specified by</Comment><br/>
<Comment># </Comment><KeywordInComment>MAN_OUTPUT</KeywordInComment><Comment>.</Comment><br/>
<Comment># The default directory is: man.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_MAN</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MAN_OUTPUT</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> man</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MAN_EXTENSION</KeywordInComment><Comment> tag determines the extension that is added to the generated</Comment><br/>
<Comment># man pages. In case the manual section does not start with a number, the number</Comment><br/>
<Comment># 3 is prepended. The dot (.) at the beginning of the </Comment><KeywordInComment>MAN_EXTENSION</KeywordInComment><Comment> tag is</Comment><br/>
<Comment># optional.</Comment><br/>
<Comment># The default value is: .3.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_MAN</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MAN_EXTENSION</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> .3</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MAN_SUBDIR</KeywordInComment><Comment> tag determines the name of the directory created within</Comment><br/>
<Comment># </Comment><KeywordInComment>MAN_OUTPUT</KeywordInComment><Comment> in which the man pages are placed. If defaults to man followed by</Comment><br/>
<Comment># </Comment><KeywordInComment>MAN_EXTENSION</KeywordInComment><Comment> with the initial . removed.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_MAN</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MAN_SUBDIR</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>MAN_LINKS</KeywordInComment><Comment> tag is set to YES and doxygen generates man output, then it</Comment><br/>
<Comment># will generate one additional man file for each entity documented in the real</Comment><br/>
<Comment># man page(s). These additional files only source the real man page, but without</Comment><br/>
<Comment># them the man command would be unable to find the correct page.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_MAN</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MAN_LINKS</Keyword><Normal Text>              </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the XML output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_XML</KeywordInComment><Comment> tag is set to YES, doxygen will generate an XML file that</Comment><br/>
<Comment># captures the structure of the code including all documentation.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_XML</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>XML_OUTPUT</KeywordInComment><Comment> tag is used to specify where the XML pages will be put. If a</Comment><br/>
<Comment># relative path is entered the value of </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> will be put in front of</Comment><br/>
<Comment># it.</Comment><br/>
<Comment># The default directory is: xml.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_XML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>XML_OUTPUT</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> xml</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>XML_PROGRAMLISTING</KeywordInComment><Comment> tag is set to YES, doxygen will dump the program</Comment><br/>
<Comment># listings (including syntax highlighting and cross-referencing information) to</Comment><br/>
<Comment># the XML output. Note that enabling this will significantly increase the size</Comment><br/>
<Comment># of the XML output.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_XML</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>XML_PROGRAMLISTING</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the DOCBOOK output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_DOCBOOK</KeywordInComment><Comment> tag is set to YES, doxygen will generate Docbook files</Comment><br/>
<Comment># that can be used to generate PDF.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_DOCBOOK</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOCBOOK_OUTPUT</KeywordInComment><Comment> tag is used to specify where the Docbook pages will be put.</Comment><br/>
<Comment># If a relative path is entered the value of </Comment><KeywordInComment>OUTPUT_DIRECTORY</KeywordInComment><Comment> will be put in</Comment><br/>
<Comment># front of it.</Comment><br/>
<Comment># The default directory is: docbook.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_DOCBOOK</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOCBOOK_OUTPUT</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> docbook</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>DOCBOOK_PROGRAMLISTING</KeywordInComment><Comment> tag is set to YES, doxygen will include the</Comment><br/>
<Comment># program listings (including syntax highlighting and cross-referencing</Comment><br/>
<Comment># information) to the DOCBOOK output. Note that enabling this will significantly</Comment><br/>
<Comment># increase the size of the DOCBOOK output.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_DOCBOOK</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOCBOOK_PROGRAMLISTING</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options for the AutoGen Definitions output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_AUTOGEN_DEF</KeywordInComment><Comment> tag is set to YES, doxygen will generate an</Comment><br/>
<Comment># AutoGen Definitions (see http://autogen.sf.net) file that captures the</Comment><br/>
<Comment># structure of the code including all documentation. Note that this feature is</Comment><br/>
<Comment># still experimental and incomplete at the moment.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_AUTOGEN_DEF</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the Perl module output</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_PERLMOD</KeywordInComment><Comment> tag is set to YES, doxygen will generate a Perl module</Comment><br/>
<Comment># file that captures the structure of the code including all documentation.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that this feature is still experimental and incomplete at the moment.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_PERLMOD</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>PERLMOD_LATEX</KeywordInComment><Comment> tag is set to YES, doxygen will generate the necessary</Comment><br/>
<Comment># Makefile rules, Perl scripts and LaTeX code to be able to generate PDF and DVI</Comment><br/>
<Comment># output from the Perl module output.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_PERLMOD</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>PERLMOD_LATEX</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>PERLMOD_PRETTY</KeywordInComment><Comment> tag is set to YES, the Perl module output will be nicely</Comment><br/>
<Comment># formatted so it can be parsed by a human reader. This is useful if you want to</Comment><br/>
<Comment># understand what is going on. On the other hand, if this tag is set to NO, the</Comment><br/>
<Comment># size of the Perl module output will be much smaller and Perl will parse it</Comment><br/>
<Comment># just the same.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_PERLMOD</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>PERLMOD_PRETTY</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The names of the make variables in the generated doxyrules.make file are</Comment><br/>
<Comment># prefixed with the string contained in </Comment><KeywordInComment>PERLMOD_MAKEVAR_PREFIX</KeywordInComment><Comment>. This is useful</Comment><br/>
<Comment># so different doxyrules.make files included by the same Makefile don't</Comment><br/>
<Comment># overwrite each other's variables.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>GENERATE_PERLMOD</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>PERLMOD_MAKEVAR_PREFIX</Keyword><Normal Text> </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the preprocessor</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> tag is set to YES, doxygen will evaluate all</Comment><br/>
<Comment># C-preprocessor directives found in the sources and include files.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>ENABLE_PREPROCESSING</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>MACRO_EXPANSION</KeywordInComment><Comment> tag is set to YES, doxygen will expand all macro names</Comment><br/>
<Comment># in the source code. If set to NO, only conditional compilation will be</Comment><br/>
<Comment># performed. Macro expansion can be done in a controlled way by setting</Comment><br/>
<Comment># </Comment><KeywordInComment>EXPAND_ONLY_PREDEF</KeywordInComment><Comment> to YES.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MACRO_EXPANSION</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXPAND_ONLY_PREDEF</KeywordInComment><Comment> and </Comment><KeywordInComment>MACRO_EXPANSION</KeywordInComment><Comment> tags are both set to YES then</Comment><br/>
<Comment># the macro expansion is limited to the macros specified with the </Comment><KeywordInComment>PREDEFINED</KeywordInComment><Comment> and</Comment><br/>
<Comment># </Comment><KeywordInComment>EXPAND_AS_DEFINED</KeywordInComment><Comment> tags.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXPAND_ONLY_PREDEF</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SEARCH_INCLUDES</KeywordInComment><Comment> tag is set to YES, the include files in the</Comment><br/>
<Comment># </Comment><KeywordInComment>INCLUDE_PATH</KeywordInComment><Comment> will be searched if a #include is found.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SEARCH_INCLUDES</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>INCLUDE_PATH</KeywordInComment><Comment> tag can be used to specify one or more directories that</Comment><br/>
<Comment># contain include files that are not </Comment><KeywordInComment>input</KeywordInComment><Comment> files but should be processed by the</Comment><br/>
<Comment># preprocessor.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>SEARCH_INCLUDES</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INCLUDE_PATH</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># You can use the </Comment><KeywordInComment>INCLUDE_FILE_PATTERNS</KeywordInComment><Comment> tag to specify one or more wildcard</Comment><br/>
<Comment># patterns (like *.h and *.hpp) to filter out the header-files in the</Comment><br/>
<Comment># directories. If left blank, the patterns specified with </Comment><KeywordInComment>FILE_PATTERNS</KeywordInComment><Comment> will be</Comment><br/>
<Comment># used.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INCLUDE_FILE_PATTERNS</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>PREDEFINED</KeywordInComment><Comment> tag can be used to specify one or more macro names that are</Comment><br/>
<Comment># defined before the preprocessor is started (similar to the -D option of e.g.</Comment><br/>
<Comment># gcc). The argument of the tag is a list of macros of the form: name or</Comment><br/>
<Comment># name=definition (no spaces). If the definition and the "=" are omitted, "=1"</Comment><br/>
<Comment># is assumed. To prevent a macro definition from being undefined via #undef or</Comment><br/>
<Comment># recursively expanded use the := operator instead of the = operator.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>PREDEFINED</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>MACRO_EXPANSION</KeywordInComment><Comment> and </Comment><KeywordInComment>EXPAND_ONLY_PREDEF</KeywordInComment><Comment> tags are set to YES then this</Comment><br/>
<Comment># tag can be used to specify a list of macro names that should be expanded. The</Comment><br/>
<Comment># macro definition that is found in the sources will be used. Use the </Comment><KeywordInComment>PREDEFINED</KeywordInComment><br/>
<Comment># tag if you want to use a different macro definition that overrules the</Comment><br/>
<Comment># definition found in the source code.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXPAND_AS_DEFINED</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>SKIP_FUNCTION_MACROS</KeywordInComment><Comment> tag is set to YES then doxygen's preprocessor will</Comment><br/>
<Comment># remove all references to function-like macros that are alone on a line, have</Comment><br/>
<Comment># an all uppercase name, and do not end with a semicolon. Such function macros</Comment><br/>
<Comment># are typically used for boiler-plate code, and will confuse the parser if not</Comment><br/>
<Comment># removed.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>SKIP_FUNCTION_MACROS</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to external references</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>TAGFILES</KeywordInComment><Comment> tag can be used to specify one or more tag files. For each tag</Comment><br/>
<Comment># file the location of the external documentation should be added. The format of</Comment><br/>
<Comment># a tag file without this location is as follows:</Comment><br/>
<Comment># </Comment><KeywordInComment>TAGFILES</KeywordInComment><Comment> = file1 file2 ...</Comment><br/>
<Comment># Adding location for the tag files is done as follows:</Comment><br/>
<Comment># </Comment><KeywordInComment>TAGFILES</KeywordInComment><Comment> = file1=loc1 "file2 = loc2" ...</Comment><br/>
<Comment># where loc1 and loc2 can be relative or absolute paths or URLs. See the</Comment><br/>
<Comment># section "Linking to external documentation" for more information about the use</Comment><br/>
<Comment># of tag files.</Comment><br/>
<Comment># Note: Each tag file must have a unique name (where the name does NOT include</Comment><br/>
<Comment># the path). If a tag file is not located in the directory in which doxygen is</Comment><br/>
<Comment># run, you must also specify the path to the tagfile here.</Comment><br/>
<Error></Error><br/>
<Keyword>TAGFILES</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># When a file name is specified after </Comment><KeywordInComment>GENERATE_TAGFILE</KeywordInComment><Comment>, doxygen will create a</Comment><br/>
<Comment># tag file that is based on the </Comment><KeywordInComment>input</KeywordInComment><Comment> files it reads. See section "Linking to</Comment><br/>
<Comment># external documentation" for more information about the usage of tag files.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_TAGFILE</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>ALLEXTERNALS</KeywordInComment><Comment> tag is set to YES, all external class will be listed in</Comment><br/>
<Comment># the class index. If set to NO, only the inherited external classes will be</Comment><br/>
<Comment># listed.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>ALLEXTERNALS</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTERNAL_GROUPS</KeywordInComment><Comment> tag is set to YES, all external groups will be listed</Comment><br/>
<Comment># in the modules index. If set to NO, only the current project's groups will be</Comment><br/>
<Comment># listed.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTERNAL_GROUPS</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>EXTERNAL_PAGES</KeywordInComment><Comment> tag is set to YES, all external pages will be listed in</Comment><br/>
<Comment># the related pages index. If set to NO, only the current project's pages will</Comment><br/>
<Comment># be listed.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>EXTERNAL_PAGES</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>PERL_PATH</KeywordInComment><Comment> should be the absolute path and name of the perl script</Comment><br/>
<Comment># interpreter (i.e. the result of 'which perl').</Comment><br/>
<Comment># The default file (with absolute path) is: /usr/bin/perl.</Comment><br/>
<Error></Error><br/>
<Keyword>PERL_PATH</Keyword><Normal Text>              </Normal Text><Assignment>=</Assignment><UntypedValue> /usr/bin/perl</UntypedValue><br/>
<Error></Error><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Comment># Configuration options related to the dot tool</Comment><br/>
<Comment>#---------------------------------------------------------------------------</Comment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>CLASS_DIAGRAMS</KeywordInComment><Comment> tag is set to YES, doxygen will generate a class diagram</Comment><br/>
<Comment># (in HTML and LaTeX) for classes with base or super classes. Setting the tag to</Comment><br/>
<Comment># NO turns the diagrams off. Note that this option also works with </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><br/>
<Comment># disabled, but it is recommended to install and use dot, since it yields more</Comment><br/>
<Comment># powerful graphs.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>CLASS_DIAGRAMS</Keyword><Normal Text>         </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># You can define message sequence charts within doxygen comments using the \msc</Comment><br/>
<Comment># command. Doxygen will then run the mscgen tool (see:</Comment><br/>
<Comment># http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the</Comment><br/>
<Comment># documentation. The </Comment><KeywordInComment>MSCGEN_PATH</KeywordInComment><Comment> tag allows you to specify the directory where</Comment><br/>
<Comment># the mscgen tool resides. If left empty the tool is assumed to be found in the</Comment><br/>
<Comment># default search path.</Comment><br/>
<Error></Error><br/>
<Keyword>MSCGEN_PATH</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># You can include diagrams made with dia in doxygen documentation. Doxygen will</Comment><br/>
<Comment># then run dia to produce the diagram and insert it in the documentation. The</Comment><br/>
<Comment># </Comment><KeywordInComment>DIA_PATH</KeywordInComment><Comment> tag allows you to specify the directory where the dia binary resides.</Comment><br/>
<Comment># If left empty dia is assumed to be found in the default search path.</Comment><br/>
<Error></Error><br/>
<Keyword>DIA_PATH</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If set to YES the inheritance and collaboration graphs will hide inheritance</Comment><br/>
<Comment># and usage relations if the target is undocumented or is not a class.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Error></Error><br/>
<Keyword>HIDE_UNDOC_RELATIONS</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If you set the </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> tag to YES then doxygen will assume the dot tool is</Comment><br/>
<Comment># available from the path. This tool is part of Graphviz (see:</Comment><br/>
<Comment># http://www.graphviz.org/), a graph visualization toolkit from AT&T and Lucent</Comment><br/>
<Comment># Bell Labs. The other options in this section have no effect if this option is</Comment><br/>
<Comment># set to NO</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Error></Error><br/>
<Keyword>HAVE_DOT</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOT_NUM_THREADS</KeywordInComment><Comment> specifies the number of dot invocations doxygen is allowed</Comment><br/>
<Comment># to run in parallel. When set to 0 doxygen will base this on the number of</Comment><br/>
<Comment># processors available in the system. You can set it explicitly to a value</Comment><br/>
<Comment># larger than 0 to get control over the balance between CPU load and processing</Comment><br/>
<Comment># speed.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 32, default value: 0.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_NUM_THREADS</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> 0</UntypedValue><br/>
<Error></Error><br/>
<Comment># When you want a differently looking font in the dot files that doxygen</Comment><br/>
<Comment># generates you can specify the font name using </Comment><KeywordInComment>DOT_FONTNAME</KeywordInComment><Comment>. You need to make</Comment><br/>
<Comment># sure dot is able to find the font, which can be done by putting it in a</Comment><br/>
<Comment># standard location or by setting the DOTFONTPATH environment variable or by</Comment><br/>
<Comment># setting </Comment><KeywordInComment>DOT_FONTPATH</KeywordInComment><Comment> to the directory containing the font.</Comment><br/>
<Comment># The default value is: Helvetica.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_FONTNAME</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> Helvetica</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOT_FONTSIZE</KeywordInComment><Comment> tag can be used to set the size (in points) of the font of</Comment><br/>
<Comment># dot graphs.</Comment><br/>
<Comment># Minimum value: 4, maximum value: 24, default value: 10.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_FONTSIZE</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> 10</UntypedValue><br/>
<Error></Error><br/>
<Comment># By default doxygen will tell dot to use the default font as specified with</Comment><br/>
<Comment># </Comment><KeywordInComment>DOT_FONTNAME</KeywordInComment><Comment>. If you specify a different font using </Comment><KeywordInComment>DOT_FONTNAME</KeywordInComment><Comment> you can set</Comment><br/>
<Comment># the path where dot can find it using this tag.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_FONTPATH</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>CLASS_GRAPH</KeywordInComment><Comment> tag is set to YES then doxygen will generate a graph for</Comment><br/>
<Comment># each documented class showing the direct and indirect inheritance relations.</Comment><br/>
<Comment># Setting this tag to YES will force the </Comment><KeywordInComment>CLASS_DIAGRAMS</KeywordInComment><Comment> tag to NO.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>CLASS_GRAPH</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>COLLABORATION_GRAPH</KeywordInComment><Comment> tag is set to YES then doxygen will generate a</Comment><br/>
<Comment># graph for each documented class showing the direct and indirect implementation</Comment><br/>
<Comment># dependencies (inheritance, containment, and class references variables) of the</Comment><br/>
<Comment># class with other documented classes.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>COLLABORATION_GRAPH</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GROUP_GRAPHS</KeywordInComment><Comment> tag is set to YES then doxygen will generate a graph for</Comment><br/>
<Comment># groups, showing the direct groups dependencies.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GROUP_GRAPHS</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>UML_LOOK</KeywordInComment><Comment> tag is set to YES, doxygen will generate inheritance and</Comment><br/>
<Comment># collaboration diagrams in a style similar to the OMG's Unified Modeling</Comment><br/>
<Comment># Language.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>UML_LOOK</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>UML_LOOK</KeywordInComment><Comment> tag is enabled, the fields and methods are shown inside the</Comment><br/>
<Comment># class node. If there are many fields or methods and many nodes the graph may</Comment><br/>
<Comment># become too big to be useful. The </Comment><KeywordInComment>UML_LIMIT_NUM_FIELDS</KeywordInComment><Comment> threshold limits the</Comment><br/>
<Comment># number of items for each type to make the size more manageable. Set this to 0</Comment><br/>
<Comment># for no limit. Note that the threshold may be exceeded by 50% before the limit</Comment><br/>
<Comment># is enforced. So when you set the threshold to 10, up to 15 fields may appear,</Comment><br/>
<Comment># but if the number exceeds 15, the total amount of fields shown is limited to</Comment><br/>
<Comment># 10.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 100, default value: 10.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>UML_LIMIT_NUM_FIELDS</Keyword><Normal Text>   </Normal Text><Assignment>=</Assignment><UntypedValue> 10</UntypedValue><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>TEMPLATE_RELATIONS</KeywordInComment><Comment> tag is set to YES then the inheritance and</Comment><br/>
<Comment># collaboration graphs will show the relations between templates and their</Comment><br/>
<Comment># instances.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>TEMPLATE_RELATIONS</Keyword><Normal Text>     </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>INCLUDE_GRAPH</KeywordInComment><Comment>, </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> and </Comment><KeywordInComment>SEARCH_INCLUDES</KeywordInComment><Comment> tags are set to</Comment><br/>
<Comment># YES then doxygen will generate a graph for each documented file showing the</Comment><br/>
<Comment># direct and indirect include dependencies of the file with other documented</Comment><br/>
<Comment># files.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INCLUDE_GRAPH</Keyword><Normal Text>          </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>INCLUDED_BY_GRAPH</KeywordInComment><Comment>, </Comment><KeywordInComment>ENABLE_PREPROCESSING</KeywordInComment><Comment> and </Comment><KeywordInComment>SEARCH_INCLUDES</KeywordInComment><Comment> tags are</Comment><br/>
<Comment># set to YES then doxygen will generate a graph for each documented file showing</Comment><br/>
<Comment># the direct and indirect include dependencies of the file with other documented</Comment><br/>
<Comment># files.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INCLUDED_BY_GRAPH</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>CALL_GRAPH</KeywordInComment><Comment> tag is set to YES then doxygen will generate a call</Comment><br/>
<Comment># dependency graph for every global function or class method.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that enabling this option will significantly increase the time of a run.</Comment><br/>
<Comment># So in most cases it will be better to enable call graphs for selected</Comment><br/>
<Comment># functions only using the \callgraph command. Disabling a call graph can be</Comment><br/>
<Comment># accomplished by means of the command \hidecallgraph.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>CALL_GRAPH</Keyword><Normal Text>             </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>CALLER_GRAPH</KeywordInComment><Comment> tag is set to YES then doxygen will generate a caller</Comment><br/>
<Comment># dependency graph for every global function or class method.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that enabling this option will significantly increase the time of a run.</Comment><br/>
<Comment># So in most cases it will be better to enable caller graphs for selected</Comment><br/>
<Comment># functions only using the \callergraph command. Disabling a caller graph can be</Comment><br/>
<Comment># accomplished by means of the command \hidecallergraph.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>CALLER_GRAPH</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GRAPHICAL_HIERARCHY</KeywordInComment><Comment> tag is set to YES then doxygen will graphical</Comment><br/>
<Comment># hierarchy of all classes instead of a textual one.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GRAPHICAL_HIERARCHY</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>DIRECTORY_GRAPH</KeywordInComment><Comment> tag is set to YES then doxygen will show the</Comment><br/>
<Comment># dependencies a directory has on other directories in a graphical way. The</Comment><br/>
<Comment># dependency relations are determined by the #include relations between the</Comment><br/>
<Comment># files in the directories.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DIRECTORY_GRAPH</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOT_IMAGE_FORMAT</KeywordInComment><Comment> tag can be used to set the image format of the images</Comment><br/>
<Comment># generated by dot. For an explanation of the image formats see the section</Comment><br/>
<Comment># output formats in the documentation of the dot tool (Graphviz (see:</Comment><br/>
<Comment># http://www.graphviz.org/)).</Comment><br/>
<Comment># Note: If you choose svg you need to set </Comment><KeywordInComment>HTML_FILE_EXTENSION</KeywordInComment><Comment> to xhtml in order</Comment><br/>
<Comment># to make the SVG files visible in IE 9+ (other browsers do not have this</Comment><br/>
<Comment># requirement).</Comment><br/>
<Comment># Possible values are: png, jpg, gif, svg, png:gd, png:gd:gd, png:cairo,</Comment><br/>
<Comment># png:cairo:gd, png:cairo:cairo, png:cairo:gdiplus, png:gdiplus and</Comment><br/>
<Comment># png:gdiplus:gdiplus.</Comment><br/>
<Comment># The default value is: png.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_IMAGE_FORMAT</Keyword><Normal Text>       </Normal Text><Assignment>=</Assignment><UntypedValue> png</UntypedValue><br/>
<Error></Error><br/>
<Comment># If </Comment><KeywordInComment>DOT_IMAGE_FORMAT</KeywordInComment><Comment> is set to svg, then this option can be set to YES to</Comment><br/>
<Comment># enable generation of interactive SVG images that allow zooming and panning.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Note that this requires a modern browser other than Internet Explorer. Tested</Comment><br/>
<Comment># and working are Firefox, Chrome, Safari, and Opera.</Comment><br/>
<Comment># Note: For IE 9+ you need to set </Comment><KeywordInComment>HTML_FILE_EXTENSION</KeywordInComment><Comment> to xhtml in order to make</Comment><br/>
<Comment># the SVG files visible. Older versions of IE do not have SVG support.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>INTERACTIVE_SVG</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOT_PATH</KeywordInComment><Comment> tag can be used to specify the path where the dot tool can be</Comment><br/>
<Comment># found. If left blank, it is assumed the dot tool can be found in the path.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_PATH</Keyword><Normal Text>               </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOTFILE_DIRS</KeywordInComment><Comment> tag can be used to specify one or more directories that</Comment><br/>
<Comment># contain dot files that are included in the documentation (see the \dotfile</Comment><br/>
<Comment># command).</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOTFILE_DIRS</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MSCFILE_DIRS</KeywordInComment><Comment> tag can be used to specify one or more directories that</Comment><br/>
<Comment># contain msc files that are included in the documentation (see the \mscfile</Comment><br/>
<Comment># command).</Comment><br/>
<Error></Error><br/>
<Keyword>MSCFILE_DIRS</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DIAFILE_DIRS</KeywordInComment><Comment> tag can be used to specify one or more directories that</Comment><br/>
<Comment># contain dia files that are included in the documentation (see the \diafile</Comment><br/>
<Comment># command).</Comment><br/>
<Error></Error><br/>
<Keyword>DIAFILE_DIRS</Keyword><Normal Text>           </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># When using plantuml, the </Comment><KeywordInComment>PLANTUML_JAR_PATH</KeywordInComment><Comment> tag should be used to specify the</Comment><br/>
<Comment># path where java can find the plantuml.jar file. If left blank, it is assumed</Comment><br/>
<Comment># PlantUML is not used or called during a preprocessing step. Doxygen will</Comment><br/>
<Comment># generate a warning when it encounters a \startuml command in this case and</Comment><br/>
<Comment># will not generate output for the diagram.</Comment><br/>
<Error></Error><br/>
<Keyword>PLANTUML_JAR_PATH</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># When using plantuml, the specified paths are searched for files specified by</Comment><br/>
<Comment># the !include statement in a plantuml block.</Comment><br/>
<Error></Error><br/>
<Keyword>PLANTUML_INCLUDE_PATH</Keyword><Normal Text>  </Normal Text><Assignment>=</Assignment><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>DOT_GRAPH_MAX_NODES</KeywordInComment><Comment> tag can be used to set the maximum number of nodes</Comment><br/>
<Comment># that will be shown in the graph. If the number of nodes in a graph becomes</Comment><br/>
<Comment># larger than this value, doxygen will truncate the graph, which is visualized</Comment><br/>
<Comment># by representing a node as a red box. Note that doxygen if the number of direct</Comment><br/>
<Comment># children of the root node in a graph is already larger than</Comment><br/>
<Comment># </Comment><KeywordInComment>DOT_GRAPH_MAX_NODES</KeywordInComment><Comment> then the graph will not be shown at all. Also note that</Comment><br/>
<Comment># the size of a graph can be further restricted by </Comment><KeywordInComment>MAX_DOT_GRAPH_DEPTH</KeywordInComment><Comment>.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 10000, default value: 50.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_GRAPH_MAX_NODES</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> 50</UntypedValue><br/>
<Error></Error><br/>
<Comment># The </Comment><KeywordInComment>MAX_DOT_GRAPH_DEPTH</KeywordInComment><Comment> tag can be used to set the maximum depth of the graphs</Comment><br/>
<Comment># generated by dot. A depth value of 3 means that only nodes reachable from the</Comment><br/>
<Comment># root by following a path via at most 3 edges will be shown. Nodes that lay</Comment><br/>
<Comment># further from the root node will be omitted. Note that setting this option to 1</Comment><br/>
<Comment># or 2 may greatly reduce the computation time needed for large code bases. Also</Comment><br/>
<Comment># note that the size of a graph can be further restricted by</Comment><br/>
<Comment># </Comment><KeywordInComment>DOT_GRAPH_MAX_NODES</KeywordInComment><Comment>. Using a depth of 0 means no depth restriction.</Comment><br/>
<Comment># Minimum value: 0, maximum value: 1000, default value: 0.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>MAX_DOT_GRAPH_DEPTH</Keyword><Normal Text>    </Normal Text><Assignment>=</Assignment><UntypedValue> 0</UntypedValue><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>DOT_TRANSPARENT</KeywordInComment><Comment> tag to YES to generate images with a transparent</Comment><br/>
<Comment># background. This is disabled by default, because dot on Windows does not seem</Comment><br/>
<Comment># to support this out of the box.</Comment><br/>
<Comment>#</Comment><br/>
<Comment># Warning: Depending on the platform used, enabling this option may lead to</Comment><br/>
<Comment># badly anti-aliased labels on the edges of a graph (i.e. they become hard to</Comment><br/>
<Comment># read).</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_TRANSPARENT</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># Set the </Comment><KeywordInComment>DOT_MULTI_TARGETS</KeywordInComment><Comment> tag to YES to allow dot to generate multiple output</Comment><br/>
<Comment># files in one run (i.e. multiple -o and -T options on the command line). This</Comment><br/>
<Comment># makes dot run faster, but since only newer versions of dot (>1.8.10) support</Comment><br/>
<Comment># this, this feature is disabled by default.</Comment><br/>
<Comment># The default value is: NO.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_MULTI_TARGETS</Keyword><Normal Text>      </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueNo>NO</ValueNo><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>GENERATE_LEGEND</KeywordInComment><Comment> tag is set to YES doxygen will generate a legend page</Comment><br/>
<Comment># explaining the meaning of the various boxes and arrows in the dot generated</Comment><br/>
<Comment># graphs.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>GENERATE_LEGEND</Keyword><Normal Text>        </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
<Error></Error><br/>
<Comment># If the </Comment><KeywordInComment>DOT_CLEANUP</KeywordInComment><Comment> tag is set to YES, doxygen will remove the intermediate dot</Comment><br/>
<Comment># files that are used to generate the various graphs.</Comment><br/>
<Comment># The default value is: YES.</Comment><br/>
<Comment># This tag requires that the tag </Comment><KeywordInComment>HAVE_DOT</KeywordInComment><Comment> is set to YES.</Comment><br/>
<Error></Error><br/>
<Keyword>DOT_CLEANUP</Keyword><Normal Text>            </Normal Text><Assignment>=</Assignment><UntypedValue> </UntypedValue><ValueYes>YES</ValueYes><br/>
