visualtest/docs/Doxyfile
changeset 7924 fcb86d323770
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/visualtest/docs/Doxyfile	Sun Nov 10 00:32:23 2013 -0500
     1.3 @@ -0,0 +1,1936 @@
     1.4 +# Doxyfile 1.8.4
     1.5 +
     1.6 +# This file describes the settings to be used by the documentation system
     1.7 +# doxygen (www.doxygen.org) for a project
     1.8 +#
     1.9 +# All text after a hash (#) is considered a comment and will be ignored
    1.10 +# The format is:
    1.11 +#       TAG = value [value, ...]
    1.12 +# For lists items can also be appended using:
    1.13 +#       TAG += value [value, ...]
    1.14 +# Values that contain spaces should be placed between quotes (" ")
    1.15 +
    1.16 +#---------------------------------------------------------------------------
    1.17 +# Project related configuration options
    1.18 +#---------------------------------------------------------------------------
    1.19 +
    1.20 +# This tag specifies the encoding used for all characters in the config file 
    1.21 +# that follow. The default is UTF-8 which is also the encoding used for all 
    1.22 +# text before the first occurrence of this tag. Doxygen uses libiconv (or the 
    1.23 +# iconv built into libc) for the transcoding. See 
    1.24 +# http://www.gnu.org/software/libiconv for the list of possible encodings.
    1.25 +
    1.26 +DOXYFILE_ENCODING      = UTF-8
    1.27 +
    1.28 +# The PROJECT_NAME tag is a single word (or sequence of words) that should 
    1.29 +# identify the project. Note that if you do not use Doxywizard you need 
    1.30 +# to put quotes around the project name if it contains spaces.
    1.31 +
    1.32 +PROJECT_NAME           = "SDL Visual Test"
    1.33 +
    1.34 +# The PROJECT_NUMBER tag can be used to enter a project or revision number. 
    1.35 +# This could be handy for archiving the generated documentation or 
    1.36 +# if some version control system is used.
    1.37 +
    1.38 +PROJECT_NUMBER         = 
    1.39 +
    1.40 +# Using the PROJECT_BRIEF tag one can provide an optional one line description 
    1.41 +# for a project that appears at the top of each page and should give viewer 
    1.42 +# a quick idea about the purpose of the project. Keep the description short.
    1.43 +
    1.44 +PROJECT_BRIEF          = 
    1.45 +
    1.46 +# With the PROJECT_LOGO tag one can specify an logo or icon that is 
    1.47 +# included in the documentation. The maximum height of the logo should not 
    1.48 +# exceed 55 pixels and the maximum width should not exceed 200 pixels. 
    1.49 +# Doxygen will copy the logo to the output directory.
    1.50 +
    1.51 +PROJECT_LOGO           = 
    1.52 +
    1.53 +# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) 
    1.54 +# base path where the generated documentation will be put. 
    1.55 +# If a relative path is entered, it will be relative to the location 
    1.56 +# where doxygen was started. If left blank the current directory will be used.
    1.57 +
    1.58 +OUTPUT_DIRECTORY       = .
    1.59 +
    1.60 +# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 
    1.61 +# 4096 sub-directories (in 2 levels) under the output directory of each output 
    1.62 +# format and will distribute the generated files over these directories. 
    1.63 +# Enabling this option can be useful when feeding doxygen a huge amount of 
    1.64 +# source files, where putting all generated files in the same directory would 
    1.65 +# otherwise cause performance problems for the file system.
    1.66 +
    1.67 +CREATE_SUBDIRS         = NO
    1.68 +
    1.69 +# The OUTPUT_LANGUAGE tag is used to specify the language in which all 
    1.70 +# documentation generated by doxygen is written. Doxygen will use this 
    1.71 +# information to generate all constant output in the proper language. 
    1.72 +# The default language is English, other supported languages are: 
    1.73 +# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 
    1.74 +# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German, 
    1.75 +# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English 
    1.76 +# messages), Korean, Korean-en, Latvian, Lithuanian, Norwegian, Macedonian, 
    1.77 +# Persian, Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, 
    1.78 +# Slovak, Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
    1.79 +
    1.80 +OUTPUT_LANGUAGE        = English
    1.81 +
    1.82 +# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will 
    1.83 +# include brief member descriptions after the members that are listed in 
    1.84 +# the file and class documentation (similar to JavaDoc). 
    1.85 +# Set to NO to disable this.
    1.86 +
    1.87 +BRIEF_MEMBER_DESC      = YES
    1.88 +
    1.89 +# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend 
    1.90 +# the brief description of a member or function before the detailed description. 
    1.91 +# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 
    1.92 +# brief descriptions will be completely suppressed.
    1.93 +
    1.94 +REPEAT_BRIEF           = YES
    1.95 +
    1.96 +# This tag implements a quasi-intelligent brief description abbreviator 
    1.97 +# that is used to form the text in various listings. Each string 
    1.98 +# in this list, if found as the leading text of the brief description, will be 
    1.99 +# stripped from the text and the result after processing the whole list, is 
   1.100 +# used as the annotated text. Otherwise, the brief description is used as-is. 
   1.101 +# If left blank, the following values are used ("$name" is automatically 
   1.102 +# replaced with the name of the entity): "The $name class" "The $name widget" 
   1.103 +# "The $name file" "is" "provides" "specifies" "contains" 
   1.104 +# "represents" "a" "an" "the"
   1.105 +
   1.106 +ABBREVIATE_BRIEF       = "The $name class" \
   1.107 +                         "The $name widget" \
   1.108 +                         "The $name file" \
   1.109 +                         is \
   1.110 +                         provides \
   1.111 +                         specifies \
   1.112 +                         contains \
   1.113 +                         represents \
   1.114 +                         a \
   1.115 +                         an \
   1.116 +                         the
   1.117 +
   1.118 +# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 
   1.119 +# Doxygen will generate a detailed section even if there is only a brief 
   1.120 +# description.
   1.121 +
   1.122 +ALWAYS_DETAILED_SEC    = NO
   1.123 +
   1.124 +# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 
   1.125 +# inherited members of a class in the documentation of that class as if those 
   1.126 +# members were ordinary class members. Constructors, destructors and assignment 
   1.127 +# operators of the base classes will not be shown.
   1.128 +
   1.129 +INLINE_INHERITED_MEMB  = NO
   1.130 +
   1.131 +# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full 
   1.132 +# path before files name in the file list and in the header files. If set 
   1.133 +# to NO the shortest path that makes the file name unique will be used.
   1.134 +
   1.135 +FULL_PATH_NAMES        = YES
   1.136 +
   1.137 +# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag 
   1.138 +# can be used to strip a user-defined part of the path. Stripping is 
   1.139 +# only done if one of the specified strings matches the left-hand part of 
   1.140 +# the path. The tag can be used to show relative paths in the file list. 
   1.141 +# If left blank the directory from which doxygen is run is used as the 
   1.142 +# path to strip. Note that you specify absolute paths here, but also 
   1.143 +# relative paths, which will be relative from the directory where doxygen is 
   1.144 +# started.
   1.145 +
   1.146 +STRIP_FROM_PATH        = 
   1.147 +
   1.148 +# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of 
   1.149 +# the path mentioned in the documentation of a class, which tells 
   1.150 +# the reader which header file to include in order to use a class. 
   1.151 +# If left blank only the name of the header file containing the class 
   1.152 +# definition is used. Otherwise one should specify the include paths that 
   1.153 +# are normally passed to the compiler using the -I flag.
   1.154 +
   1.155 +STRIP_FROM_INC_PATH    = 
   1.156 +
   1.157 +# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter 
   1.158 +# (but less readable) file names. This can be useful if your file system 
   1.159 +# doesn't support long names like on DOS, Mac, or CD-ROM.
   1.160 +
   1.161 +SHORT_NAMES            = NO
   1.162 +
   1.163 +# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen 
   1.164 +# will interpret the first line (until the first dot) of a JavaDoc-style 
   1.165 +# comment as the brief description. If set to NO, the JavaDoc 
   1.166 +# comments will behave just like regular Qt-style comments 
   1.167 +# (thus requiring an explicit @brief command for a brief description.)
   1.168 +
   1.169 +JAVADOC_AUTOBRIEF      = NO
   1.170 +
   1.171 +# If the QT_AUTOBRIEF tag is set to YES then Doxygen will 
   1.172 +# interpret the first line (until the first dot) of a Qt-style 
   1.173 +# comment as the brief description. If set to NO, the comments 
   1.174 +# will behave just like regular Qt-style comments (thus requiring 
   1.175 +# an explicit \brief command for a brief description.)
   1.176 +
   1.177 +QT_AUTOBRIEF           = NO
   1.178 +
   1.179 +# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen 
   1.180 +# treat a multi-line C++ special comment block (i.e. a block of //! or /// 
   1.181 +# comments) as a brief description. This used to be the default behaviour. 
   1.182 +# The new default is to treat a multi-line C++ comment block as a detailed 
   1.183 +# description. Set this tag to YES if you prefer the old behaviour instead.
   1.184 +
   1.185 +MULTILINE_CPP_IS_BRIEF = NO
   1.186 +
   1.187 +# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented 
   1.188 +# member inherits the documentation from any documented member that it 
   1.189 +# re-implements.
   1.190 +
   1.191 +INHERIT_DOCS           = YES
   1.192 +
   1.193 +# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce 
   1.194 +# a new page for each member. If set to NO, the documentation of a member will 
   1.195 +# be part of the file/class/namespace that contains it.
   1.196 +
   1.197 +SEPARATE_MEMBER_PAGES  = NO
   1.198 +
   1.199 +# The TAB_SIZE tag can be used to set the number of spaces in a tab. 
   1.200 +# Doxygen uses this value to replace tabs by spaces in code fragments.
   1.201 +
   1.202 +TAB_SIZE               = 4
   1.203 +
   1.204 +# This tag can be used to specify a number of aliases that acts 
   1.205 +# as commands in the documentation. An alias has the form "name=value". 
   1.206 +# For example adding "sideeffect=\par Side Effects:\n" will allow you to 
   1.207 +# put the command \sideeffect (or @sideeffect) in the documentation, which 
   1.208 +# will result in a user-defined paragraph with heading "Side Effects:". 
   1.209 +# You can put \n's in the value part of an alias to insert newlines.
   1.210 +
   1.211 +ALIASES                = 
   1.212 +
   1.213 +# This tag can be used to specify a number of word-keyword mappings (TCL only). 
   1.214 +# A mapping has the form "name=value". For example adding 
   1.215 +# "class=itcl::class" will allow you to use the command class in the 
   1.216 +# itcl::class meaning.
   1.217 +
   1.218 +TCL_SUBST              = 
   1.219 +
   1.220 +# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C 
   1.221 +# sources only. Doxygen will then generate output that is more tailored for C. 
   1.222 +# For instance, some of the names that are used will be different. The list 
   1.223 +# of all members will be omitted, etc.
   1.224 +
   1.225 +OPTIMIZE_OUTPUT_FOR_C  = YES
   1.226 +
   1.227 +# Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java 
   1.228 +# sources only. Doxygen will then generate output that is more tailored for 
   1.229 +# Java. For instance, namespaces will be presented as packages, qualified 
   1.230 +# scopes will look different, etc.
   1.231 +
   1.232 +OPTIMIZE_OUTPUT_JAVA   = NO
   1.233 +
   1.234 +# Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 
   1.235 +# sources only. Doxygen will then generate output that is more tailored for 
   1.236 +# Fortran.
   1.237 +
   1.238 +OPTIMIZE_FOR_FORTRAN   = NO
   1.239 +
   1.240 +# Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 
   1.241 +# sources. Doxygen will then generate output that is tailored for 
   1.242 +# VHDL.
   1.243 +
   1.244 +OPTIMIZE_OUTPUT_VHDL   = NO
   1.245 +
   1.246 +# Doxygen selects the parser to use depending on the extension of the files it 
   1.247 +# parses. With this tag you can assign which parser to use for a given 
   1.248 +# extension. Doxygen has a built-in mapping, but you can override or extend it 
   1.249 +# using this tag. The format is ext=language, where ext is a file extension, 
   1.250 +# and language is one of the parsers supported by doxygen: IDL, Java, 
   1.251 +# Javascript, CSharp, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, 
   1.252 +# C++. For instance to make doxygen treat .inc files as Fortran files (default 
   1.253 +# is PHP), and .f files as C (default is Fortran), use: inc=Fortran f=C. Note 
   1.254 +# that for custom extensions you also need to set FILE_PATTERNS otherwise the 
   1.255 +# files are not read by doxygen.
   1.256 +
   1.257 +EXTENSION_MAPPING      = 
   1.258 +
   1.259 +# If MARKDOWN_SUPPORT is enabled (the default) then doxygen pre-processes all 
   1.260 +# comments according to the Markdown format, which allows for more readable 
   1.261 +# documentation. See http://daringfireball.net/projects/markdown/ for details. 
   1.262 +# The output of markdown processing is further processed by doxygen, so you 
   1.263 +# can mix doxygen, HTML, and XML commands with Markdown formatting. 
   1.264 +# Disable only in case of backward compatibilities issues.
   1.265 +
   1.266 +MARKDOWN_SUPPORT       = YES
   1.267 +
   1.268 +# When enabled doxygen tries to link words that correspond to documented 
   1.269 +# classes, or namespaces to their corresponding documentation. Such a link can 
   1.270 +# be prevented in individual cases by by putting a % sign in front of the word 
   1.271 +# or globally by setting AUTOLINK_SUPPORT to NO.
   1.272 +
   1.273 +AUTOLINK_SUPPORT       = YES
   1.274 +
   1.275 +# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 
   1.276 +# to include (a tag file for) the STL sources as input, then you should 
   1.277 +# set this tag to YES in order to let doxygen match functions declarations and 
   1.278 +# definitions whose arguments contain STL classes (e.g. func(std::string); v.s. 
   1.279 +# func(std::string) {}). This also makes the inheritance and collaboration 
   1.280 +# diagrams that involve STL classes more complete and accurate.
   1.281 +
   1.282 +BUILTIN_STL_SUPPORT    = NO
   1.283 +
   1.284 +# If you use Microsoft's C++/CLI language, you should set this option to YES to 
   1.285 +# enable parsing support.
   1.286 +
   1.287 +CPP_CLI_SUPPORT        = NO
   1.288 +
   1.289 +# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 
   1.290 +# Doxygen will parse them like normal C++ but will assume all classes use public 
   1.291 +# instead of private inheritance when no explicit protection keyword is present.
   1.292 +
   1.293 +SIP_SUPPORT            = NO
   1.294 +
   1.295 +# For Microsoft's IDL there are propget and propput attributes to indicate 
   1.296 +# getter and setter methods for a property. Setting this option to YES (the 
   1.297 +# default) will make doxygen replace the get and set methods by a property in 
   1.298 +# the documentation. This will only work if the methods are indeed getting or 
   1.299 +# setting a simple type. If this is not the case, or you want to show the 
   1.300 +# methods anyway, you should set this option to NO.
   1.301 +
   1.302 +IDL_PROPERTY_SUPPORT   = YES
   1.303 +
   1.304 +# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 
   1.305 +# tag is set to YES, then doxygen will reuse the documentation of the first 
   1.306 +# member in the group (if any) for the other members of the group. By default 
   1.307 +# all members of a group must be documented explicitly.
   1.308 +
   1.309 +DISTRIBUTE_GROUP_DOC   = NO
   1.310 +
   1.311 +# Set the SUBGROUPING tag to YES (the default) to allow class member groups of 
   1.312 +# the same type (for instance a group of public functions) to be put as a 
   1.313 +# subgroup of that type (e.g. under the Public Functions section). Set it to 
   1.314 +# NO to prevent subgrouping. Alternatively, this can be done per class using 
   1.315 +# the \nosubgrouping command.
   1.316 +
   1.317 +SUBGROUPING            = YES
   1.318 +
   1.319 +# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and 
   1.320 +# unions are shown inside the group in which they are included (e.g. using 
   1.321 +# @ingroup) instead of on a separate page (for HTML and Man pages) or 
   1.322 +# section (for LaTeX and RTF).
   1.323 +
   1.324 +INLINE_GROUPED_CLASSES = NO
   1.325 +
   1.326 +# When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and 
   1.327 +# unions with only public data fields or simple typedef fields will be shown 
   1.328 +# inline in the documentation of the scope in which they are defined (i.e. file, 
   1.329 +# namespace, or group documentation), provided this scope is documented. If set 
   1.330 +# to NO (the default), structs, classes, and unions are shown on a separate 
   1.331 +# page (for HTML and Man pages) or section (for LaTeX and RTF).
   1.332 +
   1.333 +INLINE_SIMPLE_STRUCTS  = NO
   1.334 +
   1.335 +# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum 
   1.336 +# is documented as struct, union, or enum with the name of the typedef. So 
   1.337 +# typedef struct TypeS {} TypeT, will appear in the documentation as a struct 
   1.338 +# with name TypeT. When disabled the typedef will appear as a member of a file, 
   1.339 +# namespace, or class. And the struct will be named TypeS. This can typically 
   1.340 +# be useful for C code in case the coding convention dictates that all compound 
   1.341 +# types are typedef'ed and only the typedef is referenced, never the tag name.
   1.342 +
   1.343 +TYPEDEF_HIDES_STRUCT   = NO
   1.344 +
   1.345 +# The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This 
   1.346 +# cache is used to resolve symbols given their name and scope. Since this can 
   1.347 +# be an expensive process and often the same symbol appear multiple times in 
   1.348 +# the code, doxygen keeps a cache of pre-resolved symbols. If the cache is too 
   1.349 +# small doxygen will become slower. If the cache is too large, memory is wasted. 
   1.350 +# The cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid 
   1.351 +# range is 0..9, the default is 0, corresponding to a cache size of 2^16 = 65536 
   1.352 +# symbols.
   1.353 +
   1.354 +LOOKUP_CACHE_SIZE      = 0
   1.355 +
   1.356 +#---------------------------------------------------------------------------
   1.357 +# Build related configuration options
   1.358 +#---------------------------------------------------------------------------
   1.359 +
   1.360 +# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 
   1.361 +# documentation are documented, even if no documentation was available. 
   1.362 +# Private class members and static file members will be hidden unless 
   1.363 +# the EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES
   1.364 +
   1.365 +EXTRACT_ALL            = NO
   1.366 +
   1.367 +# If the EXTRACT_PRIVATE tag is set to YES all private members of a class 
   1.368 +# will be included in the documentation.
   1.369 +
   1.370 +EXTRACT_PRIVATE        = NO
   1.371 +
   1.372 +# If the EXTRACT_PACKAGE tag is set to YES all members with package or internal 
   1.373 +# scope will be included in the documentation.
   1.374 +
   1.375 +EXTRACT_PACKAGE        = NO
   1.376 +
   1.377 +# If the EXTRACT_STATIC tag is set to YES all static members of a file 
   1.378 +# will be included in the documentation.
   1.379 +
   1.380 +EXTRACT_STATIC         = NO
   1.381 +
   1.382 +# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) 
   1.383 +# defined locally in source files will be included in the documentation. 
   1.384 +# If set to NO only classes defined in header files are included.
   1.385 +
   1.386 +EXTRACT_LOCAL_CLASSES  = YES
   1.387 +
   1.388 +# This flag is only useful for Objective-C code. When set to YES local 
   1.389 +# methods, which are defined in the implementation section but not in 
   1.390 +# the interface are included in the documentation. 
   1.391 +# If set to NO (the default) only methods in the interface are included.
   1.392 +
   1.393 +EXTRACT_LOCAL_METHODS  = NO
   1.394 +
   1.395 +# If this flag is set to YES, the members of anonymous namespaces will be 
   1.396 +# extracted and appear in the documentation as a namespace called 
   1.397 +# 'anonymous_namespace{file}', where file will be replaced with the base 
   1.398 +# name of the file that contains the anonymous namespace. By default 
   1.399 +# anonymous namespaces are hidden.
   1.400 +
   1.401 +EXTRACT_ANON_NSPACES   = NO
   1.402 +
   1.403 +# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all 
   1.404 +# undocumented members of documented classes, files or namespaces. 
   1.405 +# If set to NO (the default) these members will be included in the 
   1.406 +# various overviews, but no documentation section is generated. 
   1.407 +# This option has no effect if EXTRACT_ALL is enabled.
   1.408 +
   1.409 +HIDE_UNDOC_MEMBERS     = NO
   1.410 +
   1.411 +# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all 
   1.412 +# undocumented classes that are normally visible in the class hierarchy. 
   1.413 +# If set to NO (the default) these classes will be included in the various 
   1.414 +# overviews. This option has no effect if EXTRACT_ALL is enabled.
   1.415 +
   1.416 +HIDE_UNDOC_CLASSES     = NO
   1.417 +
   1.418 +# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all 
   1.419 +# friend (class|struct|union) declarations. 
   1.420 +# If set to NO (the default) these declarations will be included in the 
   1.421 +# documentation.
   1.422 +
   1.423 +HIDE_FRIEND_COMPOUNDS  = NO
   1.424 +
   1.425 +# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any 
   1.426 +# documentation blocks found inside the body of a function. 
   1.427 +# If set to NO (the default) these blocks will be appended to the 
   1.428 +# function's detailed documentation block.
   1.429 +
   1.430 +HIDE_IN_BODY_DOCS      = NO
   1.431 +
   1.432 +# The INTERNAL_DOCS tag determines if documentation 
   1.433 +# that is typed after a \internal command is included. If the tag is set 
   1.434 +# to NO (the default) then the documentation will be excluded. 
   1.435 +# Set it to YES to include the internal documentation.
   1.436 +
   1.437 +INTERNAL_DOCS          = NO
   1.438 +
   1.439 +# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate 
   1.440 +# file names in lower-case letters. If set to YES upper-case letters are also 
   1.441 +# allowed. This is useful if you have classes or files whose names only differ 
   1.442 +# in case and if your file system supports case sensitive file names. Windows 
   1.443 +# and Mac users are advised to set this option to NO.
   1.444 +
   1.445 +CASE_SENSE_NAMES       = NO
   1.446 +
   1.447 +# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen 
   1.448 +# will show members with their full class and namespace scopes in the 
   1.449 +# documentation. If set to YES the scope will be hidden.
   1.450 +
   1.451 +HIDE_SCOPE_NAMES       = YES
   1.452 +
   1.453 +# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen 
   1.454 +# will put a list of the files that are included by a file in the documentation 
   1.455 +# of that file.
   1.456 +
   1.457 +SHOW_INCLUDE_FILES     = YES
   1.458 +
   1.459 +# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen 
   1.460 +# will list include files with double quotes in the documentation 
   1.461 +# rather than with sharp brackets.
   1.462 +
   1.463 +FORCE_LOCAL_INCLUDES   = NO
   1.464 +
   1.465 +# If the INLINE_INFO tag is set to YES (the default) then a tag [inline] 
   1.466 +# is inserted in the documentation for inline members.
   1.467 +
   1.468 +INLINE_INFO            = YES
   1.469 +
   1.470 +# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen 
   1.471 +# will sort the (detailed) documentation of file and class members 
   1.472 +# alphabetically by member name. If set to NO the members will appear in 
   1.473 +# declaration order.
   1.474 +
   1.475 +SORT_MEMBER_DOCS       = YES
   1.476 +
   1.477 +# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the 
   1.478 +# brief documentation of file, namespace and class members alphabetically 
   1.479 +# by member name. If set to NO (the default) the members will appear in 
   1.480 +# declaration order.
   1.481 +
   1.482 +SORT_BRIEF_DOCS        = NO
   1.483 +
   1.484 +# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen 
   1.485 +# will sort the (brief and detailed) documentation of class members so that 
   1.486 +# constructors and destructors are listed first. If set to NO (the default) 
   1.487 +# the constructors will appear in the respective orders defined by 
   1.488 +# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS. 
   1.489 +# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO 
   1.490 +# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
   1.491 +
   1.492 +SORT_MEMBERS_CTORS_1ST = NO
   1.493 +
   1.494 +# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the 
   1.495 +# hierarchy of group names into alphabetical order. If set to NO (the default) 
   1.496 +# the group names will appear in their defined order.
   1.497 +
   1.498 +SORT_GROUP_NAMES       = NO
   1.499 +
   1.500 +# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be 
   1.501 +# sorted by fully-qualified names, including namespaces. If set to 
   1.502 +# NO (the default), the class list will be sorted only by class name, 
   1.503 +# not including the namespace part. 
   1.504 +# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 
   1.505 +# Note: This option applies only to the class list, not to the 
   1.506 +# alphabetical list.
   1.507 +
   1.508 +SORT_BY_SCOPE_NAME     = NO
   1.509 +
   1.510 +# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to 
   1.511 +# do proper type resolution of all parameters of a function it will reject a 
   1.512 +# match between the prototype and the implementation of a member function even 
   1.513 +# if there is only one candidate or it is obvious which candidate to choose 
   1.514 +# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen 
   1.515 +# will still accept a match between prototype and implementation in such cases.
   1.516 +
   1.517 +STRICT_PROTO_MATCHING  = NO
   1.518 +
   1.519 +# The GENERATE_TODOLIST tag can be used to enable (YES) or 
   1.520 +# disable (NO) the todo list. This list is created by putting \todo 
   1.521 +# commands in the documentation.
   1.522 +
   1.523 +GENERATE_TODOLIST      = YES
   1.524 +
   1.525 +# The GENERATE_TESTLIST tag can be used to enable (YES) or 
   1.526 +# disable (NO) the test list. This list is created by putting \test 
   1.527 +# commands in the documentation.
   1.528 +
   1.529 +GENERATE_TESTLIST      = YES
   1.530 +
   1.531 +# The GENERATE_BUGLIST tag can be used to enable (YES) or 
   1.532 +# disable (NO) the bug list. This list is created by putting \bug 
   1.533 +# commands in the documentation.
   1.534 +
   1.535 +GENERATE_BUGLIST       = YES
   1.536 +
   1.537 +# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or 
   1.538 +# disable (NO) the deprecated list. This list is created by putting 
   1.539 +# \deprecated commands in the documentation.
   1.540 +
   1.541 +GENERATE_DEPRECATEDLIST= YES
   1.542 +
   1.543 +# The ENABLED_SECTIONS tag can be used to enable conditional 
   1.544 +# documentation sections, marked by \if section-label ... \endif 
   1.545 +# and \cond section-label ... \endcond blocks.
   1.546 +
   1.547 +ENABLED_SECTIONS       = 
   1.548 +
   1.549 +# The MAX_INITIALIZER_LINES tag determines the maximum number of lines 
   1.550 +# the initial value of a variable or macro consists of for it to appear in 
   1.551 +# the documentation. If the initializer consists of more lines than specified 
   1.552 +# here it will be hidden. Use a value of 0 to hide initializers completely. 
   1.553 +# The appearance of the initializer of individual variables and macros in the 
   1.554 +# documentation can be controlled using \showinitializer or \hideinitializer 
   1.555 +# command in the documentation regardless of this setting.
   1.556 +
   1.557 +MAX_INITIALIZER_LINES  = 30
   1.558 +
   1.559 +# Set the SHOW_USED_FILES tag to NO to disable the list of files generated 
   1.560 +# at the bottom of the documentation of classes and structs. If set to YES the 
   1.561 +# list will mention the files that were used to generate the documentation.
   1.562 +
   1.563 +SHOW_USED_FILES        = YES
   1.564 +
   1.565 +# Set the SHOW_FILES tag to NO to disable the generation of the Files page. 
   1.566 +# This will remove the Files entry from the Quick Index and from the 
   1.567 +# Folder Tree View (if specified). The default is YES.
   1.568 +
   1.569 +SHOW_FILES             = YES
   1.570 +
   1.571 +# Set the SHOW_NAMESPACES tag to NO to disable the generation of the 
   1.572 +# Namespaces page.  This will remove the Namespaces entry from the Quick Index 
   1.573 +# and from the Folder Tree View (if specified). The default is YES.
   1.574 +
   1.575 +SHOW_NAMESPACES        = YES
   1.576 +
   1.577 +# The FILE_VERSION_FILTER tag can be used to specify a program or script that 
   1.578 +# doxygen should invoke to get the current version for each file (typically from 
   1.579 +# the version control system). Doxygen will invoke the program by executing (via 
   1.580 +# popen()) the command <command> <input-file>, where <command> is the value of 
   1.581 +# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file 
   1.582 +# provided by doxygen. Whatever the program writes to standard output 
   1.583 +# is used as the file version. See the manual for examples.
   1.584 +
   1.585 +FILE_VERSION_FILTER    = 
   1.586 +
   1.587 +# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 
   1.588 +# by doxygen. The layout file controls the global structure of the generated 
   1.589 +# output files in an output format independent way. To create the layout file 
   1.590 +# that represents doxygen's defaults, run doxygen with the -l option. 
   1.591 +# You can optionally specify a file name after the option, if omitted 
   1.592 +# DoxygenLayout.xml will be used as the name of the layout file.
   1.593 +
   1.594 +LAYOUT_FILE            = 
   1.595 +
   1.596 +# The CITE_BIB_FILES tag can be used to specify one or more bib files 
   1.597 +# containing the references data. This must be a list of .bib files. The 
   1.598 +# .bib extension is automatically appended if omitted. Using this command 
   1.599 +# requires the bibtex tool to be installed. See also 
   1.600 +# http://en.wikipedia.org/wiki/BibTeX for more info. For LaTeX the style 
   1.601 +# of the bibliography can be controlled using LATEX_BIB_STYLE. To use this 
   1.602 +# feature you need bibtex and perl available in the search path. Do not use 
   1.603 +# file names with spaces, bibtex cannot handle them.
   1.604 +
   1.605 +CITE_BIB_FILES         = 
   1.606 +
   1.607 +#---------------------------------------------------------------------------
   1.608 +# configuration options related to warning and progress messages
   1.609 +#---------------------------------------------------------------------------
   1.610 +
   1.611 +# The QUIET tag can be used to turn on/off the messages that are generated 
   1.612 +# by doxygen. Possible values are YES and NO. If left blank NO is used.
   1.613 +
   1.614 +QUIET                  = NO
   1.615 +
   1.616 +# The WARNINGS tag can be used to turn on/off the warning messages that are 
   1.617 +# generated by doxygen. Possible values are YES and NO. If left blank 
   1.618 +# NO is used.
   1.619 +
   1.620 +WARNINGS               = YES
   1.621 +
   1.622 +# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings 
   1.623 +# for undocumented members. If EXTRACT_ALL is set to YES then this flag will 
   1.624 +# automatically be disabled.
   1.625 +
   1.626 +WARN_IF_UNDOCUMENTED   = YES
   1.627 +
   1.628 +# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for 
   1.629 +# potential errors in the documentation, such as not documenting some 
   1.630 +# parameters in a documented function, or documenting parameters that 
   1.631 +# don't exist or using markup commands wrongly.
   1.632 +
   1.633 +WARN_IF_DOC_ERROR      = YES
   1.634 +
   1.635 +# The WARN_NO_PARAMDOC option can be enabled to get warnings for 
   1.636 +# functions that are documented, but have no documentation for their parameters 
   1.637 +# or return value. If set to NO (the default) doxygen will only warn about 
   1.638 +# wrong or incomplete parameter documentation, but not about the absence of 
   1.639 +# documentation.
   1.640 +
   1.641 +WARN_NO_PARAMDOC       = NO
   1.642 +
   1.643 +# The WARN_FORMAT tag determines the format of the warning messages that 
   1.644 +# doxygen can produce. The string should contain the $file, $line, and $text 
   1.645 +# tags, which will be replaced by the file and line number from which the 
   1.646 +# warning originated and the warning text. Optionally the format may contain 
   1.647 +# $version, which will be replaced by the version of the file (if it could 
   1.648 +# be obtained via FILE_VERSION_FILTER)
   1.649 +
   1.650 +WARN_FORMAT            = "$file:$line: $text"
   1.651 +
   1.652 +# The WARN_LOGFILE tag can be used to specify a file to which warning 
   1.653 +# and error messages should be written. If left blank the output is written 
   1.654 +# to stderr.
   1.655 +
   1.656 +WARN_LOGFILE           = 
   1.657 +
   1.658 +#---------------------------------------------------------------------------
   1.659 +# configuration options related to the input files
   1.660 +#---------------------------------------------------------------------------
   1.661 +
   1.662 +# The INPUT tag can be used to specify the files and/or directories that contain 
   1.663 +# documented source files. You may enter file names like "myfile.cpp" or 
   1.664 +# directories like "/usr/src/myproject". Separate the files or directories 
   1.665 +# with spaces.
   1.666 +
   1.667 +INPUT                  = ../
   1.668 +
   1.669 +# This tag can be used to specify the character encoding of the source files 
   1.670 +# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is 
   1.671 +# also the default input encoding. Doxygen uses libiconv (or the iconv built 
   1.672 +# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for 
   1.673 +# the list of possible encodings.
   1.674 +
   1.675 +INPUT_ENCODING         = UTF-8
   1.676 +
   1.677 +# If the value of the INPUT tag contains directories, you can use the 
   1.678 +# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   1.679 +# and *.h) to filter out the source-files in the directories. If left 
   1.680 +# blank the following patterns are tested: 
   1.681 +# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh 
   1.682 +# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py 
   1.683 +# *.f90 *.f *.for *.vhd *.vhdl
   1.684 +
   1.685 +FILE_PATTERNS          = *.c \
   1.686 +                         *.cc \
   1.687 +                         *.cxx \
   1.688 +                         *.cpp \
   1.689 +                         *.c++ \
   1.690 +                         *.d \
   1.691 +                         *.java \
   1.692 +                         *.ii \
   1.693 +                         *.ixx \
   1.694 +                         *.ipp \
   1.695 +                         *.i++ \
   1.696 +                         *.inl \
   1.697 +                         *.h \
   1.698 +                         *.hh \
   1.699 +                         *.hxx \
   1.700 +                         *.hpp \
   1.701 +                         *.h++ \
   1.702 +                         *.idl \
   1.703 +                         *.odl \
   1.704 +                         *.cs \
   1.705 +                         *.php \
   1.706 +                         *.php3 \
   1.707 +                         *.inc \
   1.708 +                         *.m \
   1.709 +                         *.markdown \
   1.710 +                         *.md \
   1.711 +                         *.mm \
   1.712 +                         *.dox \
   1.713 +                         *.py \
   1.714 +                         *.f90 \
   1.715 +                         *.f \
   1.716 +                         *.for \
   1.717 +                         *.vhd \
   1.718 +                         *.vhdl \
   1.719 +                         README.txt
   1.720 +
   1.721 +# The RECURSIVE tag can be used to turn specify whether or not subdirectories 
   1.722 +# should be searched for input files as well. Possible values are YES and NO. 
   1.723 +# If left blank NO is used.
   1.724 +
   1.725 +RECURSIVE              = YES
   1.726 +
   1.727 +# The EXCLUDE tag can be used to specify files and/or directories that should be 
   1.728 +# excluded from the INPUT source files. This way you can easily exclude a 
   1.729 +# subdirectory from a directory tree whose root is specified with the INPUT tag. 
   1.730 +# Note that relative paths are relative to the directory from which doxygen is 
   1.731 +# run.
   1.732 +
   1.733 +EXCLUDE                = 
   1.734 +
   1.735 +# The EXCLUDE_SYMLINKS tag can be used to select whether or not files or 
   1.736 +# directories that are symbolic links (a Unix file system feature) are excluded 
   1.737 +# from the input.
   1.738 +
   1.739 +EXCLUDE_SYMLINKS       = NO
   1.740 +
   1.741 +# If the value of the INPUT tag contains directories, you can use the 
   1.742 +# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 
   1.743 +# certain files from those directories. Note that the wildcards are matched 
   1.744 +# against the file with absolute path, so to exclude all test directories 
   1.745 +# for example use the pattern */test/*
   1.746 +
   1.747 +EXCLUDE_PATTERNS       = 
   1.748 +
   1.749 +# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 
   1.750 +# (namespaces, classes, functions, etc.) that should be excluded from the 
   1.751 +# output. The symbol name can be a fully qualified name, a word, or if the 
   1.752 +# wildcard * is used, a substring. Examples: ANamespace, AClass, 
   1.753 +# AClass::ANamespace, ANamespace::*Test
   1.754 +
   1.755 +EXCLUDE_SYMBOLS        = 
   1.756 +
   1.757 +# The EXAMPLE_PATH tag can be used to specify one or more files or 
   1.758 +# directories that contain example code fragments that are included (see 
   1.759 +# the \include command).
   1.760 +
   1.761 +EXAMPLE_PATH           = 
   1.762 +
   1.763 +# If the value of the EXAMPLE_PATH tag contains directories, you can use the 
   1.764 +# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp 
   1.765 +# and *.h) to filter out the source-files in the directories. If left 
   1.766 +# blank all files are included.
   1.767 +
   1.768 +EXAMPLE_PATTERNS       = *
   1.769 +
   1.770 +# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 
   1.771 +# searched for input files to be used with the \include or \dontinclude 
   1.772 +# commands irrespective of the value of the RECURSIVE tag. 
   1.773 +# Possible values are YES and NO. If left blank NO is used.
   1.774 +
   1.775 +EXAMPLE_RECURSIVE      = NO
   1.776 +
   1.777 +# The IMAGE_PATH tag can be used to specify one or more files or 
   1.778 +# directories that contain image that are included in the documentation (see 
   1.779 +# the \image command).
   1.780 +
   1.781 +IMAGE_PATH             = 
   1.782 +
   1.783 +# The INPUT_FILTER tag can be used to specify a program that doxygen should 
   1.784 +# invoke to filter for each input file. Doxygen will invoke the filter program 
   1.785 +# by executing (via popen()) the command <filter> <input-file>, where <filter> 
   1.786 +# is the value of the INPUT_FILTER tag, and <input-file> is the name of an 
   1.787 +# input file. Doxygen will then use the output that the filter program writes 
   1.788 +# to standard output.  If FILTER_PATTERNS is specified, this tag will be ignored. 
   1.789 +# Note that the filter must not add or remove lines; it is applied before the 
   1.790 +# code is scanned, but not when the output code is generated. If lines are added 
   1.791 +# or removed, the anchors will not be placed correctly.
   1.792 +
   1.793 +INPUT_FILTER           = 
   1.794 +
   1.795 +# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 
   1.796 +# basis.  Doxygen will compare the file name with each pattern and apply the 
   1.797 +# filter if there is a match.  The filters are a list of the form: 
   1.798 +# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further 
   1.799 +# info on how filters are used. If FILTER_PATTERNS is empty or if 
   1.800 +# non of the patterns match the file name, INPUT_FILTER is applied.
   1.801 +
   1.802 +FILTER_PATTERNS        = 
   1.803 +
   1.804 +# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 
   1.805 +# INPUT_FILTER) will be used to filter the input files when producing source 
   1.806 +# files to browse (i.e. when SOURCE_BROWSER is set to YES).
   1.807 +
   1.808 +FILTER_SOURCE_FILES    = NO
   1.809 +
   1.810 +# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file 
   1.811 +# pattern. A pattern will override the setting for FILTER_PATTERN (if any) 
   1.812 +# and it is also possible to disable source filtering for a specific pattern 
   1.813 +# using *.ext= (so without naming a filter). This option only has effect when 
   1.814 +# FILTER_SOURCE_FILES is enabled.
   1.815 +
   1.816 +FILTER_SOURCE_PATTERNS = 
   1.817 +
   1.818 +# If the USE_MD_FILE_AS_MAINPAGE tag refers to the name of a markdown file that 
   1.819 +# is part of the input, its contents will be placed on the main page 
   1.820 +# (index.html). This can be useful if you have a project on for instance GitHub 
   1.821 +# and want reuse the introduction page also for the doxygen output.
   1.822 +
   1.823 +USE_MDFILE_AS_MAINPAGE = 
   1.824 +
   1.825 +#---------------------------------------------------------------------------
   1.826 +# configuration options related to source browsing
   1.827 +#---------------------------------------------------------------------------
   1.828 +
   1.829 +# If the SOURCE_BROWSER tag is set to YES then a list of source files will 
   1.830 +# be generated. Documented entities will be cross-referenced with these sources. 
   1.831 +# Note: To get rid of all source code in the generated output, make sure also 
   1.832 +# VERBATIM_HEADERS is set to NO.
   1.833 +
   1.834 +SOURCE_BROWSER         = NO
   1.835 +
   1.836 +# Setting the INLINE_SOURCES tag to YES will include the body 
   1.837 +# of functions and classes directly in the documentation.
   1.838 +
   1.839 +INLINE_SOURCES         = NO
   1.840 +
   1.841 +# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct 
   1.842 +# doxygen to hide any special comment blocks from generated source code 
   1.843 +# fragments. Normal C, C++ and Fortran comments will always remain visible.
   1.844 +
   1.845 +STRIP_CODE_COMMENTS    = YES
   1.846 +
   1.847 +# If the REFERENCED_BY_RELATION tag is set to YES 
   1.848 +# then for each documented function all documented 
   1.849 +# functions referencing it will be listed.
   1.850 +
   1.851 +REFERENCED_BY_RELATION = NO
   1.852 +
   1.853 +# If the REFERENCES_RELATION tag is set to YES 
   1.854 +# then for each documented function all documented entities 
   1.855 +# called/used by that function will be listed.
   1.856 +
   1.857 +REFERENCES_RELATION    = NO
   1.858 +
   1.859 +# If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 
   1.860 +# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 
   1.861 +# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 
   1.862 +# link to the source code.  Otherwise they will link to the documentation.
   1.863 +
   1.864 +REFERENCES_LINK_SOURCE = YES
   1.865 +
   1.866 +# If the USE_HTAGS tag is set to YES then the references to source code 
   1.867 +# will point to the HTML generated by the htags(1) tool instead of doxygen 
   1.868 +# built-in source browser. The htags tool is part of GNU's global source 
   1.869 +# tagging system (see http://www.gnu.org/software/global/global.html). You 
   1.870 +# will need version 4.8.6 or higher.
   1.871 +
   1.872 +USE_HTAGS              = NO
   1.873 +
   1.874 +# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen 
   1.875 +# will generate a verbatim copy of the header file for each class for 
   1.876 +# which an include is specified. Set to NO to disable this.
   1.877 +
   1.878 +VERBATIM_HEADERS       = YES
   1.879 +
   1.880 +# If CLANG_ASSISTED_PARSING is set to YES, then doxygen will use the clang parser 
   1.881 +# for more acurate parsing at the cost of reduced performance. This can be 
   1.882 +# particularly helpful with template rich C++ code for which doxygen's built-in 
   1.883 +# parser lacks the necessairy type information.
   1.884 +
   1.885 +CLANG_ASSISTED_PARSING = NO
   1.886 +
   1.887 +# If clang assisted parsing is enabled you can provide the compiler with command 
   1.888 +# line options that you would normally use when invoking the compiler. Note that 
   1.889 +# the include paths will already be set by doxygen for the files and directories 
   1.890 +# specified at INPUT and INCLUDE_PATH.
   1.891 +
   1.892 +CLANG_OPTIONS          = 
   1.893 +
   1.894 +#---------------------------------------------------------------------------
   1.895 +# configuration options related to the alphabetical class index
   1.896 +#---------------------------------------------------------------------------
   1.897 +
   1.898 +# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index 
   1.899 +# of all compounds will be generated. Enable this if the project 
   1.900 +# contains a lot of classes, structs, unions or interfaces.
   1.901 +
   1.902 +ALPHABETICAL_INDEX     = YES
   1.903 +
   1.904 +# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then 
   1.905 +# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns 
   1.906 +# in which this list will be split (can be a number in the range [1..20])
   1.907 +
   1.908 +COLS_IN_ALPHA_INDEX    = 5
   1.909 +
   1.910 +# In case all classes in a project start with a common prefix, all 
   1.911 +# classes will be put under the same header in the alphabetical index. 
   1.912 +# The IGNORE_PREFIX tag can be used to specify one or more prefixes that 
   1.913 +# should be ignored while generating the index headers.
   1.914 +
   1.915 +IGNORE_PREFIX          = 
   1.916 +
   1.917 +#---------------------------------------------------------------------------
   1.918 +# configuration options related to the HTML output
   1.919 +#---------------------------------------------------------------------------
   1.920 +
   1.921 +# If the GENERATE_HTML tag is set to YES (the default) Doxygen will 
   1.922 +# generate HTML output.
   1.923 +
   1.924 +GENERATE_HTML          = YES
   1.925 +
   1.926 +# The HTML_OUTPUT tag is used to specify where the HTML docs will be put. 
   1.927 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
   1.928 +# put in front of it. If left blank `html' will be used as the default path.
   1.929 +
   1.930 +HTML_OUTPUT            = html
   1.931 +
   1.932 +# The HTML_FILE_EXTENSION tag can be used to specify the file extension for 
   1.933 +# each generated HTML page (for example: .htm,.php,.asp). If it is left blank 
   1.934 +# doxygen will generate files with .html extension.
   1.935 +
   1.936 +HTML_FILE_EXTENSION    = .html
   1.937 +
   1.938 +# The HTML_HEADER tag can be used to specify a personal HTML header for 
   1.939 +# each generated HTML page. If it is left blank doxygen will generate a 
   1.940 +# standard header. Note that when using a custom header you are responsible  
   1.941 +# for the proper inclusion of any scripts and style sheets that doxygen 
   1.942 +# needs, which is dependent on the configuration options used. 
   1.943 +# It is advised to generate a default header using "doxygen -w html 
   1.944 +# header.html footer.html stylesheet.css YourConfigFile" and then modify 
   1.945 +# that header. Note that the header is subject to change so you typically 
   1.946 +# have to redo this when upgrading to a newer version of doxygen or when 
   1.947 +# changing the value of configuration settings such as GENERATE_TREEVIEW!
   1.948 +
   1.949 +HTML_HEADER            = 
   1.950 +
   1.951 +# The HTML_FOOTER tag can be used to specify a personal HTML footer for 
   1.952 +# each generated HTML page. If it is left blank doxygen will generate a 
   1.953 +# standard footer.
   1.954 +
   1.955 +HTML_FOOTER            = 
   1.956 +
   1.957 +# The HTML_STYLESHEET tag can be used to specify a user-defined cascading 
   1.958 +# style sheet that is used by each HTML page. It can be used to 
   1.959 +# fine-tune the look of the HTML output. If left blank doxygen will 
   1.960 +# generate a default style sheet. Note that it is recommended to use 
   1.961 +# HTML_EXTRA_STYLESHEET instead of this one, as it is more robust and this 
   1.962 +# tag will in the future become obsolete.
   1.963 +
   1.964 +HTML_STYLESHEET        = 
   1.965 +
   1.966 +# The HTML_EXTRA_STYLESHEET tag can be used to specify an additional 
   1.967 +# user-defined cascading style sheet that is included after the standard 
   1.968 +# style sheets created by doxygen. Using this option one can overrule 
   1.969 +# certain style aspects. This is preferred over using HTML_STYLESHEET 
   1.970 +# since it does not replace the standard style sheet and is therefor more 
   1.971 +# robust against future updates. Doxygen will copy the style sheet file to 
   1.972 +# the output directory.
   1.973 +
   1.974 +HTML_EXTRA_STYLESHEET  = 
   1.975 +
   1.976 +# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or 
   1.977 +# other source files which should be copied to the HTML output directory. Note 
   1.978 +# that these files will be copied to the base HTML output directory. Use the 
   1.979 +# $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these 
   1.980 +# files. In the HTML_STYLESHEET file, use the file name only. Also note that 
   1.981 +# the files will be copied as-is; there are no commands or markers available.
   1.982 +
   1.983 +HTML_EXTRA_FILES       = 
   1.984 +
   1.985 +# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. 
   1.986 +# Doxygen will adjust the colors in the style sheet and background images 
   1.987 +# according to this color. Hue is specified as an angle on a colorwheel, 
   1.988 +# see http://en.wikipedia.org/wiki/Hue for more information. 
   1.989 +# For instance the value 0 represents red, 60 is yellow, 120 is green, 
   1.990 +# 180 is cyan, 240 is blue, 300 purple, and 360 is red again. 
   1.991 +# The allowed range is 0 to 359.
   1.992 +
   1.993 +HTML_COLORSTYLE_HUE    = 220
   1.994 +
   1.995 +# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of 
   1.996 +# the colors in the HTML output. For a value of 0 the output will use 
   1.997 +# grayscales only. A value of 255 will produce the most vivid colors.
   1.998 +
   1.999 +HTML_COLORSTYLE_SAT    = 100
  1.1000 +
  1.1001 +# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to 
  1.1002 +# the luminance component of the colors in the HTML output. Values below 
  1.1003 +# 100 gradually make the output lighter, whereas values above 100 make 
  1.1004 +# the output darker. The value divided by 100 is the actual gamma applied, 
  1.1005 +# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2, 
  1.1006 +# and 100 does not change the gamma.
  1.1007 +
  1.1008 +HTML_COLORSTYLE_GAMMA  = 80
  1.1009 +
  1.1010 +# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 
  1.1011 +# page will contain the date and time when the page was generated. Setting 
  1.1012 +# this to NO can help when comparing the output of multiple runs.
  1.1013 +
  1.1014 +HTML_TIMESTAMP         = YES
  1.1015 +
  1.1016 +# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 
  1.1017 +# documentation will contain sections that can be hidden and shown after the 
  1.1018 +# page has loaded.
  1.1019 +
  1.1020 +HTML_DYNAMIC_SECTIONS  = NO
  1.1021 +
  1.1022 +# With HTML_INDEX_NUM_ENTRIES one can control the preferred number of 
  1.1023 +# entries shown in the various tree structured indices initially; the user 
  1.1024 +# can expand and collapse entries dynamically later on. Doxygen will expand 
  1.1025 +# the tree to such a level that at most the specified number of entries are 
  1.1026 +# visible (unless a fully collapsed tree already exceeds this amount). 
  1.1027 +# So setting the number of entries 1 will produce a full collapsed tree by 
  1.1028 +# default. 0 is a special value representing an infinite number of entries 
  1.1029 +# and will result in a full expanded tree by default.
  1.1030 +
  1.1031 +HTML_INDEX_NUM_ENTRIES = 100
  1.1032 +
  1.1033 +# If the GENERATE_DOCSET tag is set to YES, additional index files 
  1.1034 +# will be generated that can be used as input for Apple's Xcode 3 
  1.1035 +# integrated development environment, introduced with OSX 10.5 (Leopard). 
  1.1036 +# To create a documentation set, doxygen will generate a Makefile in the 
  1.1037 +# HTML output directory. Running make will produce the docset in that 
  1.1038 +# directory and running "make install" will install the docset in 
  1.1039 +# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find 
  1.1040 +# it at startup. 
  1.1041 +# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html 
  1.1042 +# for more information.
  1.1043 +
  1.1044 +GENERATE_DOCSET        = NO
  1.1045 +
  1.1046 +# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the 
  1.1047 +# feed. A documentation feed provides an umbrella under which multiple 
  1.1048 +# documentation sets from a single provider (such as a company or product suite) 
  1.1049 +# can be grouped.
  1.1050 +
  1.1051 +DOCSET_FEEDNAME        = "Doxygen generated docs"
  1.1052 +
  1.1053 +# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that 
  1.1054 +# should uniquely identify the documentation set bundle. This should be a 
  1.1055 +# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen 
  1.1056 +# will append .docset to the name.
  1.1057 +
  1.1058 +DOCSET_BUNDLE_ID       = org.doxygen.Project
  1.1059 +
  1.1060 +# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely 
  1.1061 +# identify the documentation publisher. This should be a reverse domain-name 
  1.1062 +# style string, e.g. com.mycompany.MyDocSet.documentation.
  1.1063 +
  1.1064 +DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
  1.1065 +
  1.1066 +# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
  1.1067 +
  1.1068 +DOCSET_PUBLISHER_NAME  = Publisher
  1.1069 +
  1.1070 +# If the GENERATE_HTMLHELP tag is set to YES, additional index files 
  1.1071 +# will be generated that can be used as input for tools like the 
  1.1072 +# Microsoft HTML help workshop to generate a compiled HTML help file (.chm) 
  1.1073 +# of the generated HTML documentation.
  1.1074 +
  1.1075 +GENERATE_HTMLHELP      = NO
  1.1076 +
  1.1077 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 
  1.1078 +# be used to specify the file name of the resulting .chm file. You 
  1.1079 +# can add a path in front of the file if the result should not be 
  1.1080 +# written to the html output directory.
  1.1081 +
  1.1082 +CHM_FILE               = 
  1.1083 +
  1.1084 +# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can 
  1.1085 +# be used to specify the location (absolute path including file name) of 
  1.1086 +# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run 
  1.1087 +# the HTML help compiler on the generated index.hhp.
  1.1088 +
  1.1089 +HHC_LOCATION           = 
  1.1090 +
  1.1091 +# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag 
  1.1092 +# controls if a separate .chi index file is generated (YES) or that 
  1.1093 +# it should be included in the master .chm file (NO).
  1.1094 +
  1.1095 +GENERATE_CHI           = NO
  1.1096 +
  1.1097 +# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING 
  1.1098 +# is used to encode HtmlHelp index (hhk), content (hhc) and project file 
  1.1099 +# content.
  1.1100 +
  1.1101 +CHM_INDEX_ENCODING     = 
  1.1102 +
  1.1103 +# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag 
  1.1104 +# controls whether a binary table of contents is generated (YES) or a 
  1.1105 +# normal table of contents (NO) in the .chm file.
  1.1106 +
  1.1107 +BINARY_TOC             = NO
  1.1108 +
  1.1109 +# The TOC_EXPAND flag can be set to YES to add extra items for group members 
  1.1110 +# to the contents of the HTML help documentation and to the tree view.
  1.1111 +
  1.1112 +TOC_EXPAND             = NO
  1.1113 +
  1.1114 +# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 
  1.1115 +# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated 
  1.1116 +# that can be used as input for Qt's qhelpgenerator to generate a 
  1.1117 +# Qt Compressed Help (.qch) of the generated HTML documentation.
  1.1118 +
  1.1119 +GENERATE_QHP           = NO
  1.1120 +
  1.1121 +# If the QHG_LOCATION tag is specified, the QCH_FILE tag can 
  1.1122 +# be used to specify the file name of the resulting .qch file. 
  1.1123 +# The path specified is relative to the HTML output folder.
  1.1124 +
  1.1125 +QCH_FILE               = 
  1.1126 +
  1.1127 +# The QHP_NAMESPACE tag specifies the namespace to use when generating 
  1.1128 +# Qt Help Project output. For more information please see 
  1.1129 +# http://doc.trolltech.com/qthelpproject.html#namespace
  1.1130 +
  1.1131 +QHP_NAMESPACE          = org.doxygen.Project
  1.1132 +
  1.1133 +# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating 
  1.1134 +# Qt Help Project output. For more information please see 
  1.1135 +# http://doc.trolltech.com/qthelpproject.html#virtual-folders
  1.1136 +
  1.1137 +QHP_VIRTUAL_FOLDER     = doc
  1.1138 +
  1.1139 +# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to 
  1.1140 +# add. For more information please see 
  1.1141 +# http://doc.trolltech.com/qthelpproject.html#custom-filters
  1.1142 +
  1.1143 +QHP_CUST_FILTER_NAME   = 
  1.1144 +
  1.1145 +# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the 
  1.1146 +# custom filter to add. For more information please see 
  1.1147 +# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters"> 
  1.1148 +# Qt Help Project / Custom Filters</a>.
  1.1149 +
  1.1150 +QHP_CUST_FILTER_ATTRS  = 
  1.1151 +
  1.1152 +# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 
  1.1153 +# project's 
  1.1154 +# filter section matches. 
  1.1155 +# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes"> 
  1.1156 +# Qt Help Project / Filter Attributes</a>.
  1.1157 +
  1.1158 +QHP_SECT_FILTER_ATTRS  = 
  1.1159 +
  1.1160 +# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can 
  1.1161 +# be used to specify the location of Qt's qhelpgenerator. 
  1.1162 +# If non-empty doxygen will try to run qhelpgenerator on the generated 
  1.1163 +# .qhp file.
  1.1164 +
  1.1165 +QHG_LOCATION           = 
  1.1166 +
  1.1167 +# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files  
  1.1168 +# will be generated, which together with the HTML files, form an Eclipse help 
  1.1169 +# plugin. To install this plugin and make it available under the help contents 
  1.1170 +# menu in Eclipse, the contents of the directory containing the HTML and XML 
  1.1171 +# files needs to be copied into the plugins directory of eclipse. The name of 
  1.1172 +# the directory within the plugins directory should be the same as 
  1.1173 +# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before 
  1.1174 +# the help appears.
  1.1175 +
  1.1176 +GENERATE_ECLIPSEHELP   = NO
  1.1177 +
  1.1178 +# A unique identifier for the eclipse help plugin. When installing the plugin 
  1.1179 +# the directory name containing the HTML and XML files should also have 
  1.1180 +# this name.
  1.1181 +
  1.1182 +ECLIPSE_DOC_ID         = org.doxygen.Project
  1.1183 +
  1.1184 +# The DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) 
  1.1185 +# at top of each HTML page. The value NO (the default) enables the index and 
  1.1186 +# the value YES disables it. Since the tabs have the same information as the 
  1.1187 +# navigation tree you can set this option to NO if you already set 
  1.1188 +# GENERATE_TREEVIEW to YES.
  1.1189 +
  1.1190 +DISABLE_INDEX          = NO
  1.1191 +
  1.1192 +# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 
  1.1193 +# structure should be generated to display hierarchical information. 
  1.1194 +# If the tag value is set to YES, a side panel will be generated 
  1.1195 +# containing a tree-like index structure (just like the one that 
  1.1196 +# is generated for HTML Help). For this to work a browser that supports 
  1.1197 +# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser). 
  1.1198 +# Windows users are probably better off using the HTML help feature. 
  1.1199 +# Since the tree basically has the same information as the tab index you 
  1.1200 +# could consider to set DISABLE_INDEX to NO when enabling this option.
  1.1201 +
  1.1202 +GENERATE_TREEVIEW      = NO
  1.1203 +
  1.1204 +# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values 
  1.1205 +# (range [0,1..20]) that doxygen will group on one line in the generated HTML 
  1.1206 +# documentation. Note that a value of 0 will completely suppress the enum 
  1.1207 +# values from appearing in the overview section.
  1.1208 +
  1.1209 +ENUM_VALUES_PER_LINE   = 4
  1.1210 +
  1.1211 +# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be 
  1.1212 +# used to set the initial width (in pixels) of the frame in which the tree 
  1.1213 +# is shown.
  1.1214 +
  1.1215 +TREEVIEW_WIDTH         = 250
  1.1216 +
  1.1217 +# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open 
  1.1218 +# links to external symbols imported via tag files in a separate window.
  1.1219 +
  1.1220 +EXT_LINKS_IN_WINDOW    = NO
  1.1221 +
  1.1222 +# Use this tag to change the font size of Latex formulas included 
  1.1223 +# as images in the HTML documentation. The default is 10. Note that 
  1.1224 +# when you change the font size after a successful doxygen run you need 
  1.1225 +# to manually remove any form_*.png images from the HTML output directory 
  1.1226 +# to force them to be regenerated.
  1.1227 +
  1.1228 +FORMULA_FONTSIZE       = 10
  1.1229 +
  1.1230 +# Use the FORMULA_TRANPARENT tag to determine whether or not the images 
  1.1231 +# generated for formulas are transparent PNGs. Transparent PNGs are 
  1.1232 +# not supported properly for IE 6.0, but are supported on all modern browsers. 
  1.1233 +# Note that when changing this option you need to delete any form_*.png files 
  1.1234 +# in the HTML output before the changes have effect.
  1.1235 +
  1.1236 +FORMULA_TRANSPARENT    = YES
  1.1237 +
  1.1238 +# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax 
  1.1239 +# (see http://www.mathjax.org) which uses client side Javascript for the 
  1.1240 +# rendering instead of using prerendered bitmaps. Use this if you do not 
  1.1241 +# have LaTeX installed or if you want to formulas look prettier in the HTML 
  1.1242 +# output. When enabled you may also need to install MathJax separately and 
  1.1243 +# configure the path to it using the MATHJAX_RELPATH option.
  1.1244 +
  1.1245 +USE_MATHJAX            = NO
  1.1246 +
  1.1247 +# When MathJax is enabled you can set the default output format to be used for 
  1.1248 +# the MathJax output. Supported types are HTML-CSS, NativeMML (i.e. MathML) and 
  1.1249 +# SVG. The default value is HTML-CSS, which is slower, but has the best 
  1.1250 +# compatibility.
  1.1251 +
  1.1252 +MATHJAX_FORMAT         = HTML-CSS
  1.1253 +
  1.1254 +# When MathJax is enabled you need to specify the location relative to the 
  1.1255 +# HTML output directory using the MATHJAX_RELPATH option. The destination 
  1.1256 +# directory should contain the MathJax.js script. For instance, if the mathjax 
  1.1257 +# directory is located at the same level as the HTML output directory, then 
  1.1258 +# MATHJAX_RELPATH should be ../mathjax. The default value points to 
  1.1259 +# the MathJax Content Delivery Network so you can quickly see the result without 
  1.1260 +# installing MathJax.  However, it is strongly recommended to install a local 
  1.1261 +# copy of MathJax from http://www.mathjax.org before deployment.
  1.1262 +
  1.1263 +MATHJAX_RELPATH        = http://cdn.mathjax.org/mathjax/latest
  1.1264 +
  1.1265 +# The MATHJAX_EXTENSIONS tag can be used to specify one or MathJax extension 
  1.1266 +# names that should be enabled during MathJax rendering.
  1.1267 +
  1.1268 +MATHJAX_EXTENSIONS     = 
  1.1269 +
  1.1270 +# The MATHJAX_CODEFILE tag can be used to specify a file with javascript 
  1.1271 +# pieces of code that will be used on startup of the MathJax code.
  1.1272 +
  1.1273 +MATHJAX_CODEFILE       = 
  1.1274 +
  1.1275 +# When the SEARCHENGINE tag is enabled doxygen will generate a search box 
  1.1276 +# for the HTML output. The underlying search engine uses javascript 
  1.1277 +# and DHTML and should work on any modern browser. Note that when using 
  1.1278 +# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets 
  1.1279 +# (GENERATE_DOCSET) there is already a search function so this one should 
  1.1280 +# typically be disabled. For large projects the javascript based search engine 
  1.1281 +# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
  1.1282 +
  1.1283 +SEARCHENGINE           = YES
  1.1284 +
  1.1285 +# When the SERVER_BASED_SEARCH tag is enabled the search engine will be 
  1.1286 +# implemented using a web server instead of a web client using Javascript. 
  1.1287 +# There are two flavours of web server based search depending on the 
  1.1288 +# EXTERNAL_SEARCH setting. When disabled, doxygen will generate a PHP script for 
  1.1289 +# searching and an index file used by the script. When EXTERNAL_SEARCH is 
  1.1290 +# enabled the indexing and searching needs to be provided by external tools. 
  1.1291 +# See the manual for details.
  1.1292 +
  1.1293 +SERVER_BASED_SEARCH    = NO
  1.1294 +
  1.1295 +# When EXTERNAL_SEARCH is enabled doxygen will no longer generate the PHP 
  1.1296 +# script for searching. Instead the search results are written to an XML file 
  1.1297 +# which needs to be processed by an external indexer. Doxygen will invoke an 
  1.1298 +# external search engine pointed to by the SEARCHENGINE_URL option to obtain 
  1.1299 +# the search results. Doxygen ships with an example indexer (doxyindexer) and 
  1.1300 +# search engine (doxysearch.cgi) which are based on the open source search 
  1.1301 +# engine library Xapian. See the manual for configuration details.
  1.1302 +
  1.1303 +EXTERNAL_SEARCH        = NO
  1.1304 +
  1.1305 +# The SEARCHENGINE_URL should point to a search engine hosted by a web server 
  1.1306 +# which will returned the search results when EXTERNAL_SEARCH is enabled. 
  1.1307 +# Doxygen ships with an example search engine (doxysearch) which is based on 
  1.1308 +# the open source search engine library Xapian. See the manual for configuration 
  1.1309 +# details.
  1.1310 +
  1.1311 +SEARCHENGINE_URL       = 
  1.1312 +
  1.1313 +# When SERVER_BASED_SEARCH and EXTERNAL_SEARCH are both enabled the unindexed 
  1.1314 +# search data is written to a file for indexing by an external tool. With the 
  1.1315 +# SEARCHDATA_FILE tag the name of this file can be specified.
  1.1316 +
  1.1317 +SEARCHDATA_FILE        = searchdata.xml
  1.1318 +
  1.1319 +# When SERVER_BASED_SEARCH AND EXTERNAL_SEARCH are both enabled the 
  1.1320 +# EXTERNAL_SEARCH_ID tag can be used as an identifier for the project. This is 
  1.1321 +# useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple 
  1.1322 +# projects and redirect the results back to the right project.
  1.1323 +
  1.1324 +EXTERNAL_SEARCH_ID     = 
  1.1325 +
  1.1326 +# The EXTRA_SEARCH_MAPPINGS tag can be used to enable searching through doxygen 
  1.1327 +# projects other than the one defined by this configuration file, but that are 
  1.1328 +# all added to the same external search index. Each project needs to have a 
  1.1329 +# unique id set via EXTERNAL_SEARCH_ID. The search mapping then maps the id 
  1.1330 +# of to a relative location where the documentation can be found. 
  1.1331 +# The format is: EXTRA_SEARCH_MAPPINGS = id1=loc1 id2=loc2 ...
  1.1332 +
  1.1333 +EXTRA_SEARCH_MAPPINGS  = 
  1.1334 +
  1.1335 +#---------------------------------------------------------------------------
  1.1336 +# configuration options related to the LaTeX output
  1.1337 +#---------------------------------------------------------------------------
  1.1338 +
  1.1339 +# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will 
  1.1340 +# generate Latex output.
  1.1341 +
  1.1342 +GENERATE_LATEX         = YES
  1.1343 +
  1.1344 +# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. 
  1.1345 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  1.1346 +# put in front of it. If left blank `latex' will be used as the default path.
  1.1347 +
  1.1348 +LATEX_OUTPUT           = latex
  1.1349 +
  1.1350 +# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be 
  1.1351 +# invoked. If left blank `latex' will be used as the default command name. 
  1.1352 +# Note that when enabling USE_PDFLATEX this option is only used for 
  1.1353 +# generating bitmaps for formulas in the HTML output, but not in the 
  1.1354 +# Makefile that is written to the output directory.
  1.1355 +
  1.1356 +LATEX_CMD_NAME         = latex
  1.1357 +
  1.1358 +# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to 
  1.1359 +# generate index for LaTeX. If left blank `makeindex' will be used as the 
  1.1360 +# default command name.
  1.1361 +
  1.1362 +MAKEINDEX_CMD_NAME     = makeindex
  1.1363 +
  1.1364 +# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact 
  1.1365 +# LaTeX documents. This may be useful for small projects and may help to 
  1.1366 +# save some trees in general.
  1.1367 +
  1.1368 +COMPACT_LATEX          = NO
  1.1369 +
  1.1370 +# The PAPER_TYPE tag can be used to set the paper type that is used 
  1.1371 +# by the printer. Possible values are: a4, letter, legal and 
  1.1372 +# executive. If left blank a4 will be used.
  1.1373 +
  1.1374 +PAPER_TYPE             = a4
  1.1375 +
  1.1376 +# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX 
  1.1377 +# packages that should be included in the LaTeX output.
  1.1378 +
  1.1379 +EXTRA_PACKAGES         = 
  1.1380 +
  1.1381 +# The LATEX_HEADER tag can be used to specify a personal LaTeX header for 
  1.1382 +# the generated latex document. The header should contain everything until 
  1.1383 +# the first chapter. If it is left blank doxygen will generate a 
  1.1384 +# standard header. Notice: only use this tag if you know what you are doing!
  1.1385 +
  1.1386 +LATEX_HEADER           = 
  1.1387 +
  1.1388 +# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for 
  1.1389 +# the generated latex document. The footer should contain everything after 
  1.1390 +# the last chapter. If it is left blank doxygen will generate a 
  1.1391 +# standard footer. Notice: only use this tag if you know what you are doing!
  1.1392 +
  1.1393 +LATEX_FOOTER           = 
  1.1394 +
  1.1395 +# The LATEX_EXTRA_FILES tag can be used to specify one or more extra images 
  1.1396 +# or other source files which should be copied to the LaTeX output directory. 
  1.1397 +# Note that the files will be copied as-is; there are no commands or markers 
  1.1398 +# available.
  1.1399 +
  1.1400 +LATEX_EXTRA_FILES      = 
  1.1401 +
  1.1402 +# If the PDF_HYPERLINKS tag is set to YES, the LaTeX that is generated 
  1.1403 +# is prepared for conversion to pdf (using ps2pdf). The pdf file will 
  1.1404 +# contain links (just like the HTML output) instead of page references 
  1.1405 +# This makes the output suitable for online browsing using a pdf viewer.
  1.1406 +
  1.1407 +PDF_HYPERLINKS         = YES
  1.1408 +
  1.1409 +# If the USE_PDFLATEX tag is set to YES, pdflatex will be used instead of 
  1.1410 +# plain latex in the generated Makefile. Set this option to YES to get a 
  1.1411 +# higher quality PDF documentation.
  1.1412 +
  1.1413 +USE_PDFLATEX           = YES
  1.1414 +
  1.1415 +# If the LATEX_BATCHMODE tag is set to YES, doxygen will add the \\batchmode. 
  1.1416 +# command to the generated LaTeX files. This will instruct LaTeX to keep 
  1.1417 +# running if errors occur, instead of asking the user for help. 
  1.1418 +# This option is also used when generating formulas in HTML.
  1.1419 +
  1.1420 +LATEX_BATCHMODE        = NO
  1.1421 +
  1.1422 +# If LATEX_HIDE_INDICES is set to YES then doxygen will not 
  1.1423 +# include the index chapters (such as File Index, Compound Index, etc.) 
  1.1424 +# in the output.
  1.1425 +
  1.1426 +LATEX_HIDE_INDICES     = NO
  1.1427 +
  1.1428 +# If LATEX_SOURCE_CODE is set to YES then doxygen will include 
  1.1429 +# source code with syntax highlighting in the LaTeX output. 
  1.1430 +# Note that which sources are shown also depends on other settings 
  1.1431 +# such as SOURCE_BROWSER.
  1.1432 +
  1.1433 +LATEX_SOURCE_CODE      = NO
  1.1434 +
  1.1435 +# The LATEX_BIB_STYLE tag can be used to specify the style to use for the 
  1.1436 +# bibliography, e.g. plainnat, or ieeetr. The default style is "plain". See 
  1.1437 +# http://en.wikipedia.org/wiki/BibTeX for more info.
  1.1438 +
  1.1439 +LATEX_BIB_STYLE        = plain
  1.1440 +
  1.1441 +#---------------------------------------------------------------------------
  1.1442 +# configuration options related to the RTF output
  1.1443 +#---------------------------------------------------------------------------
  1.1444 +
  1.1445 +# If the GENERATE_RTF tag is set to YES Doxygen will generate RTF output 
  1.1446 +# The RTF output is optimized for Word 97 and may not look very pretty with 
  1.1447 +# other RTF readers or editors.
  1.1448 +
  1.1449 +GENERATE_RTF           = NO
  1.1450 +
  1.1451 +# The RTF_OUTPUT tag is used to specify where the RTF docs will be put. 
  1.1452 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  1.1453 +# put in front of it. If left blank `rtf' will be used as the default path.
  1.1454 +
  1.1455 +RTF_OUTPUT             = rtf
  1.1456 +
  1.1457 +# If the COMPACT_RTF tag is set to YES Doxygen generates more compact 
  1.1458 +# RTF documents. This may be useful for small projects and may help to 
  1.1459 +# save some trees in general.
  1.1460 +
  1.1461 +COMPACT_RTF            = NO
  1.1462 +
  1.1463 +# If the RTF_HYPERLINKS tag is set to YES, the RTF that is generated 
  1.1464 +# will contain hyperlink fields. The RTF file will 
  1.1465 +# contain links (just like the HTML output) instead of page references. 
  1.1466 +# This makes the output suitable for online browsing using WORD or other 
  1.1467 +# programs which support those fields. 
  1.1468 +# Note: wordpad (write) and others do not support links.
  1.1469 +
  1.1470 +RTF_HYPERLINKS         = NO
  1.1471 +
  1.1472 +# Load style sheet definitions from file. Syntax is similar to doxygen's 
  1.1473 +# config file, i.e. a series of assignments. You only have to provide 
  1.1474 +# replacements, missing definitions are set to their default value.
  1.1475 +
  1.1476 +RTF_STYLESHEET_FILE    = 
  1.1477 +
  1.1478 +# Set optional variables used in the generation of an rtf document. 
  1.1479 +# Syntax is similar to doxygen's config file.
  1.1480 +
  1.1481 +RTF_EXTENSIONS_FILE    = 
  1.1482 +
  1.1483 +#---------------------------------------------------------------------------
  1.1484 +# configuration options related to the man page output
  1.1485 +#---------------------------------------------------------------------------
  1.1486 +
  1.1487 +# If the GENERATE_MAN tag is set to YES (the default) Doxygen will 
  1.1488 +# generate man pages
  1.1489 +
  1.1490 +GENERATE_MAN           = NO
  1.1491 +
  1.1492 +# The MAN_OUTPUT tag is used to specify where the man pages will be put. 
  1.1493 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  1.1494 +# put in front of it. If left blank `man' will be used as the default path.
  1.1495 +
  1.1496 +MAN_OUTPUT             = man
  1.1497 +
  1.1498 +# The MAN_EXTENSION tag determines the extension that is added to 
  1.1499 +# the generated man pages (default is the subroutine's section .3)
  1.1500 +
  1.1501 +MAN_EXTENSION          = .3
  1.1502 +
  1.1503 +# If the MAN_LINKS tag is set to YES and Doxygen generates man output, 
  1.1504 +# then it will generate one additional man file for each entity 
  1.1505 +# documented in the real man page(s). These additional files 
  1.1506 +# only source the real man page, but without them the man command 
  1.1507 +# would be unable to find the correct page. The default is NO.
  1.1508 +
  1.1509 +MAN_LINKS              = NO
  1.1510 +
  1.1511 +#---------------------------------------------------------------------------
  1.1512 +# configuration options related to the XML output
  1.1513 +#---------------------------------------------------------------------------
  1.1514 +
  1.1515 +# If the GENERATE_XML tag is set to YES Doxygen will 
  1.1516 +# generate an XML file that captures the structure of 
  1.1517 +# the code including all documentation.
  1.1518 +
  1.1519 +GENERATE_XML           = NO
  1.1520 +
  1.1521 +# The XML_OUTPUT tag is used to specify where the XML pages will be put. 
  1.1522 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be 
  1.1523 +# put in front of it. If left blank `xml' will be used as the default path.
  1.1524 +
  1.1525 +XML_OUTPUT             = xml
  1.1526 +
  1.1527 +# The XML_SCHEMA tag can be used to specify an XML schema, 
  1.1528 +# which can be used by a validating XML parser to check the 
  1.1529 +# syntax of the XML files.
  1.1530 +
  1.1531 +XML_SCHEMA             = 
  1.1532 +
  1.1533 +# The XML_DTD tag can be used to specify an XML DTD, 
  1.1534 +# which can be used by a validating XML parser to check the 
  1.1535 +# syntax of the XML files.
  1.1536 +
  1.1537 +XML_DTD                = 
  1.1538 +
  1.1539 +# If the XML_PROGRAMLISTING tag is set to YES Doxygen will 
  1.1540 +# dump the program listings (including syntax highlighting 
  1.1541 +# and cross-referencing information) to the XML output. Note that 
  1.1542 +# enabling this will significantly increase the size of the XML output.
  1.1543 +
  1.1544 +XML_PROGRAMLISTING     = YES
  1.1545 +
  1.1546 +#---------------------------------------------------------------------------
  1.1547 +# configuration options related to the DOCBOOK output
  1.1548 +#---------------------------------------------------------------------------
  1.1549 +
  1.1550 +# If the GENERATE_DOCBOOK tag is set to YES Doxygen will generate DOCBOOK files 
  1.1551 +# that can be used to generate PDF.
  1.1552 +
  1.1553 +GENERATE_DOCBOOK       = NO
  1.1554 +
  1.1555 +# The DOCBOOK_OUTPUT tag is used to specify where the DOCBOOK pages will be put. 
  1.1556 +# If a relative path is entered the value of OUTPUT_DIRECTORY will be put in 
  1.1557 +# front of it. If left blank docbook will be used as the default path.
  1.1558 +
  1.1559 +DOCBOOK_OUTPUT         = docbook
  1.1560 +
  1.1561 +#---------------------------------------------------------------------------
  1.1562 +# configuration options for the AutoGen Definitions output
  1.1563 +#---------------------------------------------------------------------------
  1.1564 +
  1.1565 +# If the GENERATE_AUTOGEN_DEF tag is set to YES Doxygen will 
  1.1566 +# generate an AutoGen Definitions (see autogen.sf.net) file 
  1.1567 +# that captures the structure of the code including all 
  1.1568 +# documentation. Note that this feature is still experimental 
  1.1569 +# and incomplete at the moment.
  1.1570 +
  1.1571 +GENERATE_AUTOGEN_DEF   = NO
  1.1572 +
  1.1573 +#---------------------------------------------------------------------------
  1.1574 +# configuration options related to the Perl module output
  1.1575 +#---------------------------------------------------------------------------
  1.1576 +
  1.1577 +# If the GENERATE_PERLMOD tag is set to YES Doxygen will 
  1.1578 +# generate a Perl module file that captures the structure of 
  1.1579 +# the code including all documentation. Note that this 
  1.1580 +# feature is still experimental and incomplete at the 
  1.1581 +# moment.
  1.1582 +
  1.1583 +GENERATE_PERLMOD       = NO
  1.1584 +
  1.1585 +# If the PERLMOD_LATEX tag is set to YES Doxygen will generate 
  1.1586 +# the necessary Makefile rules, Perl scripts and LaTeX code to be able 
  1.1587 +# to generate PDF and DVI output from the Perl module output.
  1.1588 +
  1.1589 +PERLMOD_LATEX          = NO
  1.1590 +
  1.1591 +# If the PERLMOD_PRETTY tag is set to YES the Perl module output will be 
  1.1592 +# nicely formatted so it can be parsed by a human reader.  This is useful 
  1.1593 +# if you want to understand what is going on.  On the other hand, if this 
  1.1594 +# tag is set to NO the size of the Perl module output will be much smaller 
  1.1595 +# and Perl will parse it just the same.
  1.1596 +
  1.1597 +PERLMOD_PRETTY         = YES
  1.1598 +
  1.1599 +# The names of the make variables in the generated doxyrules.make file 
  1.1600 +# are prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. 
  1.1601 +# This is useful so different doxyrules.make files included by the same 
  1.1602 +# Makefile don't overwrite each other's variables.
  1.1603 +
  1.1604 +PERLMOD_MAKEVAR_PREFIX = 
  1.1605 +
  1.1606 +#---------------------------------------------------------------------------
  1.1607 +# Configuration options related to the preprocessor
  1.1608 +#---------------------------------------------------------------------------
  1.1609 +
  1.1610 +# If the ENABLE_PREPROCESSING tag is set to YES (the default) Doxygen will 
  1.1611 +# evaluate all C-preprocessor directives found in the sources and include 
  1.1612 +# files.
  1.1613 +
  1.1614 +ENABLE_PREPROCESSING   = YES
  1.1615 +
  1.1616 +# If the MACRO_EXPANSION tag is set to YES Doxygen will expand all macro 
  1.1617 +# names in the source code. If set to NO (the default) only conditional 
  1.1618 +# compilation will be performed. Macro expansion can be done in a controlled 
  1.1619 +# way by setting EXPAND_ONLY_PREDEF to YES.
  1.1620 +
  1.1621 +MACRO_EXPANSION        = NO
  1.1622 +
  1.1623 +# If the EXPAND_ONLY_PREDEF and MACRO_EXPANSION tags are both set to YES 
  1.1624 +# then the macro expansion is limited to the macros specified with the 
  1.1625 +# PREDEFINED and EXPAND_AS_DEFINED tags.
  1.1626 +
  1.1627 +EXPAND_ONLY_PREDEF     = NO
  1.1628 +
  1.1629 +# If the SEARCH_INCLUDES tag is set to YES (the default) the includes files 
  1.1630 +# pointed to by INCLUDE_PATH will be searched when a #include is found.
  1.1631 +
  1.1632 +SEARCH_INCLUDES        = YES
  1.1633 +
  1.1634 +# The INCLUDE_PATH tag can be used to specify one or more directories that 
  1.1635 +# contain include files that are not input files but should be processed by 
  1.1636 +# the preprocessor.
  1.1637 +
  1.1638 +INCLUDE_PATH           = 
  1.1639 +
  1.1640 +# You can use the INCLUDE_FILE_PATTERNS tag to specify one or more wildcard 
  1.1641 +# patterns (like *.h and *.hpp) to filter out the header-files in the 
  1.1642 +# directories. If left blank, the patterns specified with FILE_PATTERNS will 
  1.1643 +# be used.
  1.1644 +
  1.1645 +INCLUDE_FILE_PATTERNS  = 
  1.1646 +
  1.1647 +# The PREDEFINED tag can be used to specify one or more macro names that 
  1.1648 +# are defined before the preprocessor is started (similar to the -D option of 
  1.1649 +# gcc). The argument of the tag is a list of macros of the form: name 
  1.1650 +# or name=definition (no spaces). If the definition and the = are 
  1.1651 +# omitted =1 is assumed. To prevent a macro definition from being 
  1.1652 +# undefined via #undef or recursively expanded use the := operator 
  1.1653 +# instead of the = operator.
  1.1654 +
  1.1655 +PREDEFINED             = 
  1.1656 +
  1.1657 +# If the MACRO_EXPANSION and EXPAND_ONLY_PREDEF tags are set to YES then 
  1.1658 +# this tag can be used to specify a list of macro names that should be expanded. 
  1.1659 +# The macro definition that is found in the sources will be used. 
  1.1660 +# Use the PREDEFINED tag if you want to use a different macro definition that 
  1.1661 +# overrules the definition found in the source code.
  1.1662 +
  1.1663 +EXPAND_AS_DEFINED      = 
  1.1664 +
  1.1665 +# If the SKIP_FUNCTION_MACROS tag is set to YES (the default) then 
  1.1666 +# doxygen's preprocessor will remove all references to function-like macros 
  1.1667 +# that are alone on a line, have an all uppercase name, and do not end with a 
  1.1668 +# semicolon, because these will confuse the parser if not removed.
  1.1669 +
  1.1670 +SKIP_FUNCTION_MACROS   = YES
  1.1671 +
  1.1672 +#---------------------------------------------------------------------------
  1.1673 +# Configuration::additions related to external references
  1.1674 +#---------------------------------------------------------------------------
  1.1675 +
  1.1676 +# The TAGFILES option can be used to specify one or more tagfiles. For each 
  1.1677 +# tag file the location of the external documentation should be added. The 
  1.1678 +# format of a tag file without this location is as follows: 
  1.1679 +#   TAGFILES = file1 file2 ... 
  1.1680 +# Adding location for the tag files is done as follows: 
  1.1681 +#   TAGFILES = file1=loc1 "file2 = loc2" ... 
  1.1682 +# where "loc1" and "loc2" can be relative or absolute paths 
  1.1683 +# or URLs. Note that each tag file must have a unique name (where the name does 
  1.1684 +# NOT include the path). If a tag file is not located in the directory in which 
  1.1685 +# doxygen is run, you must also specify the path to the tagfile here.
  1.1686 +
  1.1687 +TAGFILES               = 
  1.1688 +
  1.1689 +# When a file name is specified after GENERATE_TAGFILE, doxygen will create 
  1.1690 +# a tag file that is based on the input files it reads.
  1.1691 +
  1.1692 +GENERATE_TAGFILE       = 
  1.1693 +
  1.1694 +# If the ALLEXTERNALS tag is set to YES all external classes will be listed 
  1.1695 +# in the class index. If set to NO only the inherited external classes 
  1.1696 +# will be listed.
  1.1697 +
  1.1698 +ALLEXTERNALS           = NO
  1.1699 +
  1.1700 +# If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed 
  1.1701 +# in the modules index. If set to NO, only the current project's groups will 
  1.1702 +# be listed.
  1.1703 +
  1.1704 +EXTERNAL_GROUPS        = YES
  1.1705 +
  1.1706 +# If the EXTERNAL_PAGES tag is set to YES all external pages will be listed 
  1.1707 +# in the related pages index. If set to NO, only the current project's 
  1.1708 +# pages will be listed.
  1.1709 +
  1.1710 +EXTERNAL_PAGES         = YES
  1.1711 +
  1.1712 +# The PERL_PATH should be the absolute path and name of the perl script 
  1.1713 +# interpreter (i.e. the result of `which perl').
  1.1714 +
  1.1715 +PERL_PATH              = /usr/bin/perl
  1.1716 +
  1.1717 +#---------------------------------------------------------------------------
  1.1718 +# Configuration options related to the dot tool
  1.1719 +#---------------------------------------------------------------------------
  1.1720 +
  1.1721 +# If the CLASS_DIAGRAMS tag is set to YES (the default) Doxygen will 
  1.1722 +# generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base 
  1.1723 +# or super classes. Setting the tag to NO turns the diagrams off. Note that 
  1.1724 +# this option also works with HAVE_DOT disabled, but it is recommended to 
  1.1725 +# install and use dot, since it yields more powerful graphs.
  1.1726 +
  1.1727 +CLASS_DIAGRAMS         = YES
  1.1728 +
  1.1729 +# You can define message sequence charts within doxygen comments using the \msc 
  1.1730 +# command. Doxygen will then run the mscgen tool (see 
  1.1731 +# http://www.mcternan.me.uk/mscgen/) to produce the chart and insert it in the 
  1.1732 +# documentation. The MSCGEN_PATH tag allows you to specify the directory where 
  1.1733 +# the mscgen tool resides. If left empty the tool is assumed to be found in the 
  1.1734 +# default search path.
  1.1735 +
  1.1736 +MSCGEN_PATH            = 
  1.1737 +
  1.1738 +# If set to YES, the inheritance and collaboration graphs will hide 
  1.1739 +# inheritance and usage relations if the target is undocumented 
  1.1740 +# or is not a class.
  1.1741 +
  1.1742 +HIDE_UNDOC_RELATIONS   = YES
  1.1743 +
  1.1744 +# If you set the HAVE_DOT tag to YES then doxygen will assume the dot tool is 
  1.1745 +# available from the path. This tool is part of Graphviz, a graph visualization 
  1.1746 +# toolkit from AT&T and Lucent Bell Labs. The other options in this section 
  1.1747 +# have no effect if this option is set to NO (the default)
  1.1748 +
  1.1749 +HAVE_DOT               = NO
  1.1750 +
  1.1751 +# The DOT_NUM_THREADS specifies the number of dot invocations doxygen is 
  1.1752 +# allowed to run in parallel. When set to 0 (the default) doxygen will 
  1.1753 +# base this on the number of processors available in the system. You can set it 
  1.1754 +# explicitly to a value larger than 0 to get control over the balance 
  1.1755 +# between CPU load and processing speed.
  1.1756 +
  1.1757 +DOT_NUM_THREADS        = 0
  1.1758 +
  1.1759 +# By default doxygen will use the Helvetica font for all dot files that 
  1.1760 +# doxygen generates. When you want a differently looking font you can specify 
  1.1761 +# the font name using DOT_FONTNAME. You need to make sure dot is able to find 
  1.1762 +# the font, which can be done by putting it in a standard location or by setting 
  1.1763 +# the DOTFONTPATH environment variable or by setting DOT_FONTPATH to the 
  1.1764 +# directory containing the font.
  1.1765 +
  1.1766 +DOT_FONTNAME           = Helvetica
  1.1767 +
  1.1768 +# The DOT_FONTSIZE tag can be used to set the size of the font of dot graphs. 
  1.1769 +# The default size is 10pt.
  1.1770 +
  1.1771 +DOT_FONTSIZE           = 10
  1.1772 +
  1.1773 +# By default doxygen will tell dot to use the Helvetica font. 
  1.1774 +# If you specify a different font using DOT_FONTNAME you can use DOT_FONTPATH to 
  1.1775 +# set the path where dot can find it.
  1.1776 +
  1.1777 +DOT_FONTPATH           = 
  1.1778 +
  1.1779 +# If the CLASS_GRAPH and HAVE_DOT tags are set to YES then doxygen 
  1.1780 +# will generate a graph for each documented class showing the direct and 
  1.1781 +# indirect inheritance relations. Setting this tag to YES will force the 
  1.1782 +# CLASS_DIAGRAMS tag to NO.
  1.1783 +
  1.1784 +CLASS_GRAPH            = YES
  1.1785 +
  1.1786 +# If the COLLABORATION_GRAPH and HAVE_DOT tags are set to YES then doxygen 
  1.1787 +# will generate a graph for each documented class showing the direct and 
  1.1788 +# indirect implementation dependencies (inheritance, containment, and 
  1.1789 +# class references variables) of the class with other documented classes.
  1.1790 +
  1.1791 +COLLABORATION_GRAPH    = YES
  1.1792 +
  1.1793 +# If the GROUP_GRAPHS and HAVE_DOT tags are set to YES then doxygen 
  1.1794 +# will generate a graph for groups, showing the direct groups dependencies
  1.1795 +
  1.1796 +GROUP_GRAPHS           = YES
  1.1797 +
  1.1798 +# If the UML_LOOK tag is set to YES doxygen will generate inheritance and 
  1.1799 +# collaboration diagrams in a style similar to the OMG's Unified Modeling 
  1.1800 +# Language.
  1.1801 +
  1.1802 +UML_LOOK               = NO
  1.1803 +
  1.1804 +# If the UML_LOOK tag is enabled, the fields and methods are shown inside 
  1.1805 +# the class node. If there are many fields or methods and many nodes the 
  1.1806 +# graph may become too big to be useful. The UML_LIMIT_NUM_FIELDS 
  1.1807 +# threshold limits the number of items for each type to make the size more 
  1.1808 +# manageable. Set this to 0 for no limit. Note that the threshold may be 
  1.1809 +# exceeded by 50% before the limit is enforced.
  1.1810 +
  1.1811 +UML_LIMIT_NUM_FIELDS   = 10
  1.1812 +
  1.1813 +# If set to YES, the inheritance and collaboration graphs will show the 
  1.1814 +# relations between templates and their instances.
  1.1815 +
  1.1816 +TEMPLATE_RELATIONS     = NO
  1.1817 +
  1.1818 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDE_GRAPH, and HAVE_DOT 
  1.1819 +# tags are set to YES then doxygen will generate a graph for each documented 
  1.1820 +# file showing the direct and indirect include dependencies of the file with 
  1.1821 +# other documented files.
  1.1822 +
  1.1823 +INCLUDE_GRAPH          = YES
  1.1824 +
  1.1825 +# If the ENABLE_PREPROCESSING, SEARCH_INCLUDES, INCLUDED_BY_GRAPH, and 
  1.1826 +# HAVE_DOT tags are set to YES then doxygen will generate a graph for each 
  1.1827 +# documented header file showing the documented files that directly or 
  1.1828 +# indirectly include this file.
  1.1829 +
  1.1830 +INCLUDED_BY_GRAPH      = YES
  1.1831 +
  1.1832 +# If the CALL_GRAPH and HAVE_DOT options are set to YES then 
  1.1833 +# doxygen will generate a call dependency graph for every global function 
  1.1834 +# or class method. Note that enabling this option will significantly increase 
  1.1835 +# the time of a run. So in most cases it will be better to enable call graphs 
  1.1836 +# for selected functions only using the \callgraph command.
  1.1837 +
  1.1838 +CALL_GRAPH             = NO
  1.1839 +
  1.1840 +# If the CALLER_GRAPH and HAVE_DOT tags are set to YES then 
  1.1841 +# doxygen will generate a caller dependency graph for every global function 
  1.1842 +# or class method. Note that enabling this option will significantly increase 
  1.1843 +# the time of a run. So in most cases it will be better to enable caller 
  1.1844 +# graphs for selected functions only using the \callergraph command.
  1.1845 +
  1.1846 +CALLER_GRAPH           = NO
  1.1847 +
  1.1848 +# If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 
  1.1849 +# will generate a graphical hierarchy of all classes instead of a textual one.
  1.1850 +
  1.1851 +GRAPHICAL_HIERARCHY    = YES
  1.1852 +
  1.1853 +# If the DIRECTORY_GRAPH and HAVE_DOT tags are set to YES 
  1.1854 +# then doxygen will show the dependencies a directory has on other directories 
  1.1855 +# in a graphical way. The dependency relations are determined by the #include 
  1.1856 +# relations between the files in the directories.
  1.1857 +
  1.1858 +DIRECTORY_GRAPH        = YES
  1.1859 +
  1.1860 +# The DOT_IMAGE_FORMAT tag can be used to set the image format of the images 
  1.1861 +# generated by dot. Possible values are svg, png, jpg, or gif. 
  1.1862 +# If left blank png will be used. If you choose svg you need to set 
  1.1863 +# HTML_FILE_EXTENSION to xhtml in order to make the SVG files 
  1.1864 +# visible in IE 9+ (other browsers do not have this requirement).
  1.1865 +
  1.1866 +DOT_IMAGE_FORMAT       = png
  1.1867 +
  1.1868 +# If DOT_IMAGE_FORMAT is set to svg, then this option can be set to YES to 
  1.1869 +# enable generation of interactive SVG images that allow zooming and panning. 
  1.1870 +# Note that this requires a modern browser other than Internet Explorer. 
  1.1871 +# Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you 
  1.1872 +# need to set HTML_FILE_EXTENSION to xhtml in order to make the SVG files 
  1.1873 +# visible. Older versions of IE do not have SVG support.
  1.1874 +
  1.1875 +INTERACTIVE_SVG        = NO
  1.1876 +
  1.1877 +# The tag DOT_PATH can be used to specify the path where the dot tool can be 
  1.1878 +# found. If left blank, it is assumed the dot tool can be found in the path.
  1.1879 +
  1.1880 +DOT_PATH               = 
  1.1881 +
  1.1882 +# The DOTFILE_DIRS tag can be used to specify one or more directories that 
  1.1883 +# contain dot files that are included in the documentation (see the 
  1.1884 +# \dotfile command).
  1.1885 +
  1.1886 +DOTFILE_DIRS           = 
  1.1887 +
  1.1888 +# The MSCFILE_DIRS tag can be used to specify one or more directories that 
  1.1889 +# contain msc files that are included in the documentation (see the 
  1.1890 +# \mscfile command).
  1.1891 +
  1.1892 +MSCFILE_DIRS           = 
  1.1893 +
  1.1894 +# The DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 
  1.1895 +# nodes that will be shown in the graph. If the number of nodes in a graph 
  1.1896 +# becomes larger than this value, doxygen will truncate the graph, which is 
  1.1897 +# visualized by representing a node as a red box. Note that doxygen if the 
  1.1898 +# number of direct children of the root node in a graph is already larger than 
  1.1899 +# DOT_GRAPH_MAX_NODES then the graph will not be shown at all. Also note 
  1.1900 +# that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
  1.1901 +
  1.1902 +DOT_GRAPH_MAX_NODES    = 50
  1.1903 +
  1.1904 +# The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the 
  1.1905 +# graphs generated by dot. A depth value of 3 means that only nodes reachable 
  1.1906 +# from the root by following a path via at most 3 edges will be shown. Nodes 
  1.1907 +# that lay further from the root node will be omitted. Note that setting this 
  1.1908 +# option to 1 or 2 may greatly reduce the computation time needed for large 
  1.1909 +# code bases. Also note that the size of a graph can be further restricted by 
  1.1910 +# DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
  1.1911 +
  1.1912 +MAX_DOT_GRAPH_DEPTH    = 0
  1.1913 +
  1.1914 +# Set the DOT_TRANSPARENT tag to YES to generate images with a transparent 
  1.1915 +# background. This is disabled by default, because dot on Windows does not 
  1.1916 +# seem to support this out of the box. Warning: Depending on the platform used, 
  1.1917 +# enabling this option may lead to badly anti-aliased labels on the edges of 
  1.1918 +# a graph (i.e. they become hard to read).
  1.1919 +
  1.1920 +DOT_TRANSPARENT        = NO
  1.1921 +
  1.1922 +# Set the DOT_MULTI_TARGETS tag to YES allow dot to generate multiple output 
  1.1923 +# files in one run (i.e. multiple -o and -T options on the command line). This 
  1.1924 +# makes dot run faster, but since only newer versions of dot (>1.8.10) 
  1.1925 +# support this, this feature is disabled by default.
  1.1926 +
  1.1927 +DOT_MULTI_TARGETS      = NO
  1.1928 +
  1.1929 +# If the GENERATE_LEGEND tag is set to YES (the default) Doxygen will 
  1.1930 +# generate a legend page explaining the meaning of the various boxes and 
  1.1931 +# arrows in the dot generated graphs.
  1.1932 +
  1.1933 +GENERATE_LEGEND        = YES
  1.1934 +
  1.1935 +# If the DOT_CLEANUP tag is set to YES (the default) Doxygen will 
  1.1936 +# remove the intermediate dot files that are used to generate 
  1.1937 +# the various graphs.
  1.1938 +
  1.1939 +DOT_CLEANUP            = YES