Skip to content
This repository
Browse code

Nearing beta

  • Loading branch information...
commit 943328b9892ee0c77e64bfaa67e4b831d409ff42 1 parent dcb4b31
authored
1  .gitignore
... ...
@@ -1,3 +1,4 @@
  1
+doc
1 2
 *.dylib
2 3
 *.o
3 4
 moc_*
2  config.pri
@@ -2,7 +2,7 @@ CONFIG -= debug release_and_debug
2 2
 CONFIG += release
3 3
 
4 4
 mac:CONFIG += x86
5  
-QMAKE_MAC_SDK=/Developer/SDKs/MacOSX10.6.sdk
  5
+#QMAKE_MAC_SDK=/Developer/SDKs/MacOSX10.6.sdk
6 6
 unix:QMAKE_DEL_FILE=rm -rf
7 7
 win32:CONFIG -= embed_manifest_dll
8 8
 
1,697  doxygen.conf
... ...
@@ -0,0 +1,1697 @@
  1
+# Doxyfile 1.7.4
  2
+
  3
+# This file describes the settings to be used by the documentation system
  4
+# doxygen (www.doxygen.org) for a project.
  5
+#
  6
+# All text after a hash (#) is considered a comment and will be ignored.
  7
+# The format is:
  8
+#       TAG = value [value, ...]
  9
+# For lists items can also be appended using:
  10
+#       TAG += value [value, ...]
  11
+# Values that contain spaces should be placed between quotes (" ").
  12
+
  13
+#---------------------------------------------------------------------------
  14
+# Project related configuration options
  15
+#---------------------------------------------------------------------------
  16
+
  17
+# This tag specifies the encoding used for all characters in the config file
  18
+# that follow. The default is UTF-8 which is also the encoding used for all
  19
+# text before the first occurrence of this tag. Doxygen uses libiconv (or the
  20
+# iconv built into libc) for the transcoding. See
  21
+# http://www.gnu.org/software/libiconv for the list of possible encodings.
  22
+
  23
+DOXYFILE_ENCODING      = UTF-8
  24
+
  25
+# The PROJECT_NAME tag is a single word (or a sequence of words surrounded
  26
+# by quotes) that should identify the project.
  27
+
  28
+PROJECT_NAME           = "KISS IDE"
  29
+
  30
+# The PROJECT_NUMBER tag can be used to enter a project or revision number.
  31
+# This could be handy for archiving the generated documentation or
  32
+# if some version control system is used.
  33
+
  34
+PROJECT_NUMBER         =
  35
+
  36
+# Using the PROJECT_BRIEF tag one can provide an optional one line description
  37
+# for a project that appears at the top of each page and should give viewer
  38
+# a quick idea about the purpose of the project. Keep the description short.
  39
+
  40
+PROJECT_BRIEF          = "An extensible IDE tailored to robotics development"
  41
+
  42
+# With the PROJECT_LOGO tag one can specify an logo or icon that is
  43
+# included in the documentation. The maximum height of the logo should not
  44
+# exceed 55 pixels and the maximum width should not exceed 200 pixels.
  45
+# Doxygen will copy the logo to the output directory.
  46
+
  47
+PROJECT_LOGO           = trademarks/logos/icon.png
  48
+
  49
+# The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute)
  50
+# base path where the generated documentation will be put.
  51
+# If a relative path is entered, it will be relative to the location
  52
+# where doxygen was started. If left blank the current directory will be used.
  53
+
  54
+OUTPUT_DIRECTORY       = doc
  55
+
  56
+# If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
  57
+# 4096 sub-directories (in 2 levels) under the output directory of each output
  58
+# format and will distribute the generated files over these directories.
  59
+# Enabling this option can be useful when feeding doxygen a huge amount of
  60
+# source files, where putting all generated files in the same directory would
  61
+# otherwise cause performance problems for the file system.
  62
+
  63
+CREATE_SUBDIRS         = NO
  64
+
  65
+# The OUTPUT_LANGUAGE tag is used to specify the language in which all
  66
+# documentation generated by doxygen is written. Doxygen will use this
  67
+# information to generate all constant output in the proper language.
  68
+# The default language is English, other supported languages are:
  69
+# Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional,
  70
+# Croatian, Czech, Danish, Dutch, Esperanto, Farsi, Finnish, French, German,
  71
+# Greek, Hungarian, Italian, Japanese, Japanese-en (Japanese with English
  72
+# messages), Korean, Korean-en, Lithuanian, Norwegian, Macedonian, Persian,
  73
+# Polish, Portuguese, Romanian, Russian, Serbian, Serbian-Cyrillic, Slovak,
  74
+# Slovene, Spanish, Swedish, Ukrainian, and Vietnamese.
  75
+
  76
+OUTPUT_LANGUAGE        = English
  77
+
  78
+# If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
  79
+# include brief member descriptions after the members that are listed in
  80
+# the file and class documentation (similar to JavaDoc).
  81
+# Set to NO to disable this.
  82
+
  83
+BRIEF_MEMBER_DESC      = YES
  84
+
  85
+# If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
  86
+# the brief description of a member or function before the detailed description.
  87
+# Note: if both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the
  88
+# brief descriptions will be completely suppressed.
  89
+
  90
+REPEAT_BRIEF           = YES
  91
+
  92
+# This tag implements a quasi-intelligent brief description abbreviator
  93
+# that is used to form the text in various listings. Each string
  94
+# in this list, if found as the leading text of the brief description, will be
  95
+# stripped from the text and the result after processing the whole list, is
  96
+# used as the annotated text. Otherwise, the brief description is used as-is.
  97
+# If left blank, the following values are used ("$name" is automatically
  98
+# replaced with the name of the entity): "The $name class" "The $name widget"
  99
+# "The $name file" "is" "provides" "specifies" "contains"
  100
+# "represents" "a" "an" "the"
  101
+
  102
+ABBREVIATE_BRIEF       =
  103
+
  104
+# If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then
  105
+# Doxygen will generate a detailed section even if there is only a brief
  106
+# description.
  107
+
  108
+ALWAYS_DETAILED_SEC    = NO
  109
+
  110
+# If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all
  111
+# inherited members of a class in the documentation of that class as if those
  112
+# members were ordinary class members. Constructors, destructors and assignment
  113
+# operators of the base classes will not be shown.
  114
+
  115
+INLINE_INHERITED_MEMB  = NO
  116
+
  117
+# If the FULL_PATH_NAMES tag is set to YES then Doxygen will prepend the full
  118
+# path before files name in the file list and in the header files. If set
  119
+# to NO the shortest path that makes the file name unique will be used.
  120
+
  121
+FULL_PATH_NAMES        = YES
  122
+
  123
+# If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag
  124
+# can be used to strip a user-defined part of the path. Stripping is
  125
+# only done if one of the specified strings matches the left-hand part of
  126
+# the path. The tag can be used to show relative paths in the file list.
  127
+# If left blank the directory from which doxygen is run is used as the
  128
+# path to strip.
  129
+
  130
+STRIP_FROM_PATH        =
  131
+
  132
+# The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
  133
+# the path mentioned in the documentation of a class, which tells
  134
+# the reader which header file to include in order to use a class.
  135
+# If left blank only the name of the header file containing the class
  136
+# definition is used. Otherwise one should specify the include paths that
  137
+# are normally passed to the compiler using the -I flag.
  138
+
  139
+STRIP_FROM_INC_PATH    =
  140
+
  141
+# If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter
  142
+# (but less readable) file names. This can be useful if your file system
  143
+# doesn't support long names like on DOS, Mac, or CD-ROM.
  144
+
  145
+SHORT_NAMES            = NO
  146
+
  147
+# If the JAVADOC_AUTOBRIEF tag is set to YES then Doxygen
  148
+# will interpret the first line (until the first dot) of a JavaDoc-style
  149
+# comment as the brief description. If set to NO, the JavaDoc
  150
+# comments will behave just like regular Qt-style comments
  151
+# (thus requiring an explicit @brief command for a brief description.)
  152
+
  153
+JAVADOC_AUTOBRIEF      = NO
  154
+
  155
+# If the QT_AUTOBRIEF tag is set to YES then Doxygen will
  156
+# interpret the first line (until the first dot) of a Qt-style
  157
+# comment as the brief description. If set to NO, the comments
  158
+# will behave just like regular Qt-style comments (thus requiring
  159
+# an explicit \brief command for a brief description.)
  160
+
  161
+QT_AUTOBRIEF           = NO
  162
+
  163
+# The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen
  164
+# treat a multi-line C++ special comment block (i.e. a block of //! or ///
  165
+# comments) as a brief description. This used to be the default behaviour.
  166
+# The new default is to treat a multi-line C++ comment block as a detailed
  167
+# description. Set this tag to YES if you prefer the old behaviour instead.
  168
+
  169
+MULTILINE_CPP_IS_BRIEF = NO
  170
+
  171
+# If the INHERIT_DOCS tag is set to YES (the default) then an undocumented
  172
+# member inherits the documentation from any documented member that it
  173
+# re-implements.
  174
+
  175
+INHERIT_DOCS           = YES
  176
+
  177
+# If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce
  178
+# a new page for each member. If set to NO, the documentation of a member will
  179
+# be part of the file/class/namespace that contains it.
  180
+
  181
+SEPARATE_MEMBER_PAGES  = NO
  182
+
  183
+# The TAB_SIZE tag can be used to set the number of spaces in a tab.
  184
+# Doxygen uses this value to replace tabs by spaces in code fragments.
  185
+
  186
+TAB_SIZE               = 8
  187
+
  188
+# This tag can be used to specify a number of aliases that acts
  189
+# as commands in the documentation. An alias has the form "name=value".
  190
+# For example adding "sideeffect=\par Side Effects:\n" will allow you to
  191
+# put the command \sideeffect (or @sideeffect) in the documentation, which
  192
+# will result in a user-defined paragraph with heading "Side Effects:".
  193
+# You can put \n's in the value part of an alias to insert newlines.
  194
+
  195
+ALIASES                =
  196
+
  197
+# Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C
  198
+# sources only. Doxygen will then generate output that is more tailored for C.
  199
+# For instance, some of the names that are used will be different. The list
  200
+# of all members will be omitted, etc.
  201
+
  202
+OPTIMIZE_OUTPUT_FOR_C  = NO
  203
+
  204
+# Doxygen selects the parser to use depending on the extension of the files it
  205
+# parses. With this tag you can assign which parser to use for a given extension.
  206
+# Doxygen has a built-in mapping, but you can override or extend it using this
  207
+# tag. The format is ext=language, where ext is a file extension, and language
  208
+# is one of the parsers supported by doxygen: IDL, Java, Javascript, CSharp, C,
  209
+# C++, D, PHP, Objective-C, Python, Fortran, VHDL, C, C++. For instance to make
  210
+# doxygen treat .inc files as Fortran files (default is PHP), and .f files as C
  211
+# (default is Fortran), use: inc=Fortran f=C. Note that for custom extensions
  212
+# you also need to set FILE_PATTERNS otherwise the files are not read by doxygen.
  213
+
  214
+EXTENSION_MAPPING      =
  215
+
  216
+# If you use STL classes (i.e. std::string, std::vector, etc.) but do not want
  217
+# to include (a tag file for) the STL sources as input, then you should
  218
+# set this tag to YES in order to let doxygen match functions declarations and
  219
+# definitions whose arguments contain STL classes (e.g. func(std::string); v.s.
  220
+# func(std::string) {}). This also makes the inheritance and collaboration
  221
+# diagrams that involve STL classes more complete and accurate.
  222
+
  223
+BUILTIN_STL_SUPPORT    = NO
  224
+
  225
+# If you use Microsoft's C++/CLI language, you should set this option to YES to
  226
+# enable parsing support.
  227
+
  228
+CPP_CLI_SUPPORT        = NO
  229
+
  230
+# Set the SIP_SUPPORT tag to YES if your project consists of sip sources only.
  231
+# Doxygen will parse them like normal C++ but will assume all classes use public
  232
+# instead of private inheritance when no explicit protection keyword is present.
  233
+
  234
+SIP_SUPPORT            = NO
  235
+
  236
+# For Microsoft's IDL there are propget and propput attributes to indicate getter
  237
+# and setter methods for a property. Setting this option to YES (the default)
  238
+# will make doxygen replace the get and set methods by a property in the
  239
+# documentation. This will only work if the methods are indeed getting or
  240
+# setting a simple type. If this is not the case, or you want to show the
  241
+# methods anyway, you should set this option to NO.
  242
+
  243
+IDL_PROPERTY_SUPPORT   = YES
  244
+
  245
+# If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
  246
+# tag is set to YES, then doxygen will reuse the documentation of the first
  247
+# member in the group (if any) for the other members of the group. By default
  248
+# all members of a group must be documented explicitly.
  249
+
  250
+DISTRIBUTE_GROUP_DOC   = NO
  251
+
  252
+# Set the SUBGROUPING tag to YES (the default) to allow class member groups of
  253
+# the same type (for instance a group of public functions) to be put as a
  254
+# subgroup of that type (e.g. under the Public Functions section). Set it to
  255
+# NO to prevent subgrouping. Alternatively, this can be done per class using
  256
+# the \nosubgrouping command.
  257
+
  258
+SUBGROUPING            = YES
  259
+
  260
+# When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and
  261
+# unions are shown inside the group in which they are included (e.g. using
  262
+# @ingroup) instead of on a separate page (for HTML and Man pages) or
  263
+# section (for LaTeX and RTF).
  264
+
  265
+INLINE_GROUPED_CLASSES = NO
  266
+
  267
+# When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
  268
+# is documented as struct, union, or enum with the name of the typedef. So
  269
+# typedef struct TypeS {} TypeT, will appear in the documentation as a struct
  270
+# with name TypeT. When disabled the typedef will appear as a member of a file,
  271
+# namespace, or class. And the struct will be named TypeS. This can typically
  272
+# be useful for C code in case the coding convention dictates that all compound
  273
+# types are typedef'ed and only the typedef is referenced, never the tag name.
  274
+
  275
+TYPEDEF_HIDES_STRUCT   = NO
  276
+
  277
+# The SYMBOL_CACHE_SIZE determines the size of the internal cache use to
  278
+# determine which symbols to keep in memory and which to flush to disk.
  279
+# When the cache is full, less often used symbols will be written to disk.
  280
+# For small to medium size projects (<1000 input files) the default value is
  281
+# probably good enough. For larger projects a too small cache size can cause
  282
+# doxygen to be busy swapping symbols to and from disk most of the time
  283
+# causing a significant performance penalty.
  284
+# If the system has enough physical memory increasing the cache will improve the
  285
+# performance by keeping more symbols in memory. Note that the value works on
  286
+# a logarithmic scale so increasing the size by one will roughly double the
  287
+# memory usage. The cache size is given by this formula:
  288
+# 2^(16+SYMBOL_CACHE_SIZE). The valid range is 0..9, the default is 0,
  289
+# corresponding to a cache size of 2^16 = 65536 symbols
  290
+
  291
+SYMBOL_CACHE_SIZE      = 0
  292
+
  293
+#---------------------------------------------------------------------------
  294
+# Build related configuration options
  295
+#---------------------------------------------------------------------------
  296
+
  297
+# If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
  298
+# documentation are documented, even if no documentation was available.
  299
+# Private class members and static file members will be hidden unless
  300
+# the EXTRACT_PRIVATE and EXTRACT_STATIC tags are set to YES
  301
+
  302
+EXTRACT_ALL            = NO
  303
+
  304
+# If the EXTRACT_PRIVATE tag is set to YES all private members of a class
  305
+# will be included in the documentation.
  306
+
  307
+EXTRACT_PRIVATE        = NO
  308
+
  309
+# If the EXTRACT_STATIC tag is set to YES all static members of a file
  310
+# will be included in the documentation.
  311
+
  312
+EXTRACT_STATIC         = NO
  313
+
  314
+# If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs)
  315
+# defined locally in source files will be included in the documentation.
  316
+# If set to NO only classes defined in header files are included.
  317
+
  318
+EXTRACT_LOCAL_CLASSES  = YES
  319
+
  320
+# This flag is only useful for Objective-C code. When set to YES local
  321
+# methods, which are defined in the implementation section but not in
  322
+# the interface are included in the documentation.
  323
+# If set to NO (the default) only methods in the interface are included.
  324
+
  325
+EXTRACT_LOCAL_METHODS  = NO
  326
+
  327
+# If this flag is set to YES, the members of anonymous namespaces will be
  328
+# extracted and appear in the documentation as a namespace called
  329
+# 'anonymous_namespace{file}', where file will be replaced with the base
  330
+# name of the file that contains the anonymous namespace. By default
  331
+# anonymous namespaces are hidden.
  332
+
  333
+EXTRACT_ANON_NSPACES   = NO
  334
+
  335
+# If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all
  336
+# undocumented members of documented classes, files or namespaces.
  337
+# If set to NO (the default) these members will be included in the
  338
+# various overviews, but no documentation section is generated.
  339
+# This option has no effect if EXTRACT_ALL is enabled.
  340
+
  341
+HIDE_UNDOC_MEMBERS     = NO
  342
+
  343
+# If the HIDE_UNDOC_CLASSES tag is set to YES, Doxygen will hide all
  344
+# undocumented classes that are normally visible in the class hierarchy.
  345
+# If set to NO (the default) these classes will be included in the various
  346
+# overviews. This option has no effect if EXTRACT_ALL is enabled.
  347
+
  348
+HIDE_UNDOC_CLASSES     = NO
  349
+
  350
+# If the HIDE_FRIEND_COMPOUNDS tag is set to YES, Doxygen will hide all
  351
+# friend (class|struct|union) declarations.
  352
+# If set to NO (the default) these declarations will be included in the
  353
+# documentation.
  354
+
  355
+HIDE_FRIEND_COMPOUNDS  = NO
  356
+
  357
+# If the HIDE_IN_BODY_DOCS tag is set to YES, Doxygen will hide any
  358
+# documentation blocks found inside the body of a function.
  359
+# If set to NO (the default) these blocks will be appended to the
  360
+# function's detailed documentation block.
  361
+
  362
+HIDE_IN_BODY_DOCS      = NO
  363
+
  364
+# The INTERNAL_DOCS tag determines if documentation
  365
+# that is typed after a \internal command is included. If the tag is set
  366
+# to NO (the default) then the documentation will be excluded.
  367
+# Set it to YES to include the internal documentation.
  368
+
  369
+INTERNAL_DOCS          = NO
  370
+
  371
+# If the CASE_SENSE_NAMES tag is set to NO then Doxygen will only generate
  372
+# file names in lower-case letters. If set to YES upper-case letters are also
  373
+# allowed. This is useful if you have classes or files whose names only differ
  374
+# in case and if your file system supports case sensitive file names. Windows
  375
+# and Mac users are advised to set this option to NO.
  376
+
  377
+CASE_SENSE_NAMES       = NO
  378
+
  379
+# If the HIDE_SCOPE_NAMES tag is set to NO (the default) then Doxygen
  380
+# will show members with their full class and namespace scopes in the
  381
+# documentation. If set to YES the scope will be hidden.
  382
+
  383
+HIDE_SCOPE_NAMES       = NO
  384
+
  385
+# If the SHOW_INCLUDE_FILES tag is set to YES (the default) then Doxygen
  386
+# will put a list of the files that are included by a file in the documentation
  387
+# of that file.
  388
+
  389
+SHOW_INCLUDE_FILES     = YES
  390
+
  391
+# If the FORCE_LOCAL_INCLUDES tag is set to YES then Doxygen
  392
+# will list include files with double quotes in the documentation
  393
+# rather than with sharp brackets.
  394
+
  395
+FORCE_LOCAL_INCLUDES   = NO
  396
+
  397
+# If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
  398
+# is inserted in the documentation for inline members.
  399
+
  400
+INLINE_INFO            = YES
  401
+
  402
+# If the SORT_MEMBER_DOCS tag is set to YES (the default) then doxygen
  403
+# will sort the (detailed) documentation of file and class members
  404
+# alphabetically by member name. If set to NO the members will appear in
  405
+# declaration order.
  406
+
  407
+SORT_MEMBER_DOCS       = YES
  408
+
  409
+# If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the
  410
+# brief documentation of file, namespace and class members alphabetically
  411
+# by member name. If set to NO (the default) the members will appear in
  412
+# declaration order.
  413
+
  414
+SORT_BRIEF_DOCS        = NO
  415
+
  416
+# If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen
  417
+# will sort the (brief and detailed) documentation of class members so that
  418
+# constructors and destructors are listed first. If set to NO (the default)
  419
+# the constructors will appear in the respective orders defined by
  420
+# SORT_MEMBER_DOCS and SORT_BRIEF_DOCS.
  421
+# This tag will be ignored for brief docs if SORT_BRIEF_DOCS is set to NO
  422
+# and ignored for detailed docs if SORT_MEMBER_DOCS is set to NO.
  423
+
  424
+SORT_MEMBERS_CTORS_1ST = NO
  425
+
  426
+# If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the
  427
+# hierarchy of group names into alphabetical order. If set to NO (the default)
  428
+# the group names will appear in their defined order.
  429
+
  430
+SORT_GROUP_NAMES       = NO
  431
+
  432
+# If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be
  433
+# sorted by fully-qualified names, including namespaces. If set to
  434
+# NO (the default), the class list will be sorted only by class name,
  435
+# not including the namespace part.
  436
+# Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES.
  437
+# Note: This option applies only to the class list, not to the
  438
+# alphabetical list.
  439
+
  440
+SORT_BY_SCOPE_NAME     = NO
  441
+
  442
+# If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to
  443
+# do proper type resolution of all parameters of a function it will reject a
  444
+# match between the prototype and the implementation of a member function even
  445
+# if there is only one candidate or it is obvious which candidate to choose
  446
+# by doing a simple string match. By disabling STRICT_PROTO_MATCHING doxygen
  447
+# will still accept a match between prototype and implementation in such cases.
  448
+
  449
+STRICT_PROTO_MATCHING  = NO
  450
+
  451
+# The GENERATE_TODOLIST tag can be used to enable (YES) or
  452
+# disable (NO) the todo list. This list is created by putting \todo
  453
+# commands in the documentation.
  454
+
  455
+GENERATE_TODOLIST      = YES
  456
+
  457
+# The GENERATE_TESTLIST tag can be used to enable (YES) or
  458
+# disable (NO) the test list. This list is created by putting \test
  459
+# commands in the documentation.
  460
+
  461
+GENERATE_TESTLIST      = YES
  462
+
  463
+# The GENERATE_BUGLIST tag can be used to enable (YES) or
  464
+# disable (NO) the bug list. This list is created by putting \bug
  465
+# commands in the documentation.
  466
+
  467
+GENERATE_BUGLIST       = YES
  468
+
  469
+# The GENERATE_DEPRECATEDLIST tag can be used to enable (YES) or
  470
+# disable (NO) the deprecated list. This list is created by putting
  471
+# \deprecated commands in the documentation.
  472
+
  473
+GENERATE_DEPRECATEDLIST= YES
  474
+
  475
+# The ENABLED_SECTIONS tag can be used to enable conditional
  476
+# documentation sections, marked by \if sectionname ... \endif.
  477
+
  478
+ENABLED_SECTIONS       =
  479
+
  480
+# The MAX_INITIALIZER_LINES tag determines the maximum number of lines
  481
+# the initial value of a variable or macro consists of for it to appear in
  482
+# the documentation. If the initializer consists of more lines than specified
  483
+# here it will be hidden. Use a value of 0 to hide initializers completely.
  484
+# The appearance of the initializer of individual variables and macros in the
  485
+# documentation can be controlled using \showinitializer or \hideinitializer
  486
+# command in the documentation regardless of this setting.
  487
+
  488
+MAX_INITIALIZER_LINES  = 30
  489
+
  490
+# Set the SHOW_USED_FILES tag to NO to disable the list of files generated
  491
+# at the bottom of the documentation of classes and structs. If set to YES the
  492
+# list will mention the files that were used to generate the documentation.
  493
+
  494
+SHOW_USED_FILES        = YES
  495
+
  496
+# If the sources in your project are distributed over multiple directories
  497
+# then setting the SHOW_DIRECTORIES tag to YES will show the directory hierarchy
  498
+# in the documentation. The default is NO.
  499
+
  500
+SHOW_DIRECTORIES       = NO
  501
+
  502
+# Set the SHOW_FILES tag to NO to disable the generation of the Files page.
  503
+# This will remove the Files entry from the Quick Index and from the
  504
+# Folder Tree View (if specified). The default is YES.
  505
+
  506
+SHOW_FILES             = YES
  507
+
  508
+# Set the SHOW_NAMESPACES tag to NO to disable the generation of the
  509
+# Namespaces page.
  510
+# This will remove the Namespaces entry from the Quick Index
  511
+# and from the Folder Tree View (if specified). The default is YES.
  512
+
  513
+SHOW_NAMESPACES        = YES
  514
+
  515
+# The FILE_VERSION_FILTER tag can be used to specify a program or script that
  516
+# doxygen should invoke to get the current version for each file (typically from
  517
+# the version control system). Doxygen will invoke the program by executing (via
  518
+# popen()) the command <command> <input-file>, where <command> is the value of
  519
+# the FILE_VERSION_FILTER tag, and <input-file> is the name of an input file
  520
+# provided by doxygen. Whatever the program writes to standard output
  521
+# is used as the file version. See the manual for examples.
  522
+
  523
+FILE_VERSION_FILTER    =
  524
+
  525
+# The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
  526
+# by doxygen. The layout file controls the global structure of the generated
  527
+# output files in an output format independent way. The create the layout file
  528
+# that represents doxygen's defaults, run doxygen with the -l option.
  529
+# You can optionally specify a file name after the option, if omitted
  530
+# DoxygenLayout.xml will be used as the name of the layout file.
  531
+
  532
+LAYOUT_FILE            =
  533
+
  534
+#---------------------------------------------------------------------------
  535
+# configuration options related to warning and progress messages
  536
+#---------------------------------------------------------------------------
  537
+
  538
+# The QUIET tag can be used to turn on/off the messages that are generated
  539
+# by doxygen. Possible values are YES and NO. If left blank NO is used.
  540
+
  541
+QUIET                  = NO
  542
+
  543
+# The WARNINGS tag can be used to turn on/off the warning messages that are
  544
+# generated by doxygen. Possible values are YES and NO. If left blank
  545
+# NO is used.
  546
+
  547
+WARNINGS               = YES
  548
+
  549
+# If WARN_IF_UNDOCUMENTED is set to YES, then doxygen will generate warnings
  550
+# for undocumented members. If EXTRACT_ALL is set to YES then this flag will
  551
+# automatically be disabled.
  552
+
  553
+WARN_IF_UNDOCUMENTED   = YES
  554
+
  555
+# If WARN_IF_DOC_ERROR is set to YES, doxygen will generate warnings for
  556
+# potential errors in the documentation, such as not documenting some
  557
+# parameters in a documented function, or documenting parameters that
  558
+# don't exist or using markup commands wrongly.
  559
+
  560
+WARN_IF_DOC_ERROR      = YES
  561
+
  562
+# The WARN_NO_PARAMDOC option can be enabled to get warnings for
  563
+# functions that are documented, but have no documentation for their parameters
  564
+# or return value. If set to NO (the default) doxygen will only warn about
  565
+# wrong or incomplete parameter documentation, but not about the absence of
  566
+# documentation.
  567
+
  568
+WARN_NO_PARAMDOC       = NO
  569
+
  570
+# The WARN_FORMAT tag determines the format of the warning messages that
  571
+# doxygen can produce. The string should contain the $file, $line, and $text
  572
+# tags, which will be replaced by the file and line number from which the
  573
+# warning originated and the warning text. Optionally the format may contain
  574
+# $version, which will be replaced by the version of the file (if it could
  575
+# be obtained via FILE_VERSION_FILTER)
  576
+
  577
+WARN_FORMAT            = "$file:$line: $text"
  578
+
  579
+# The WARN_LOGFILE tag can be used to specify a file to which warning
  580
+# and error messages should be written. If left blank the output is written
  581
+# to stderr.
  582
+
  583
+WARN_LOGFILE           =
  584
+
  585
+#---------------------------------------------------------------------------
  586
+# configuration options related to the input files
  587
+#---------------------------------------------------------------------------
  588
+
  589
+# The INPUT tag can be used to specify the files and/or directories that contain
  590
+# documented source files. You may enter file names like "myfile.cpp" or
  591
+# directories like "/usr/src/myproject". Separate the files or directories
  592
+# with spaces.
  593
+
  594
+INPUT                  = src include
  595
+
  596
+# This tag can be used to specify the character encoding of the source files
  597
+# that doxygen parses. Internally doxygen uses the UTF-8 encoding, which is
  598
+# also the default input encoding. Doxygen uses libiconv (or the iconv built
  599
+# into libc) for the transcoding. See http://www.gnu.org/software/libiconv for
  600
+# the list of possible encodings.
  601
+
  602
+INPUT_ENCODING         = UTF-8
  603
+
  604
+# If the value of the INPUT tag contains directories, you can use the
  605
+# FILE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
  606
+# and *.h) to filter out the source-files in the directories. If left
  607
+# blank the following patterns are tested:
  608
+# *.c *.cc *.cxx *.cpp *.c++ *.d *.java *.ii *.ixx *.ipp *.i++ *.inl *.h *.hh
  609
+# *.hxx *.hpp *.h++ *.idl *.odl *.cs *.php *.php3 *.inc *.m *.mm *.dox *.py
  610
+# *.f90 *.f *.for *.vhd *.vhdl
  611
+
  612
+FILE_PATTERNS          =
  613
+
  614
+# The RECURSIVE tag can be used to turn specify whether or not subdirectories
  615
+# should be searched for input files as well. Possible values are YES and NO.
  616
+# If left blank NO is used.
  617
+
  618
+RECURSIVE              = YES
  619
+
  620
+# The EXCLUDE tag can be used to specify files and/or directories that should
  621
+# excluded from the INPUT source files. This way you can easily exclude a
  622
+# subdirectory from a directory tree whose root is specified with the INPUT tag.
  623
+
  624
+EXCLUDE                =
  625
+
  626
+# The EXCLUDE_SYMLINKS tag can be used select whether or not files or
  627
+# directories that are symbolic links (a Unix file system feature) are excluded
  628
+# from the input.
  629
+
  630
+EXCLUDE_SYMLINKS       = NO
  631
+
  632
+# If the value of the INPUT tag contains directories, you can use the
  633
+# EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude
  634
+# certain files from those directories. Note that the wildcards are matched
  635
+# against the file with absolute path, so to exclude all test directories
  636
+# for example use the pattern */test/*
  637
+
  638
+EXCLUDE_PATTERNS       =
  639
+
  640
+# The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names
  641
+# (namespaces, classes, functions, etc.) that should be excluded from the
  642
+# output. The symbol name can be a fully qualified name, a word, or if the
  643
+# wildcard * is used, a substring. Examples: ANamespace, AClass,
  644
+# AClass::ANamespace, ANamespace::*Test
  645
+
  646
+EXCLUDE_SYMBOLS        =
  647
+
  648
+# The EXAMPLE_PATH tag can be used to specify one or more files or
  649
+# directories that contain example code fragments that are included (see
  650
+# the \include command).
  651
+
  652
+EXAMPLE_PATH           =
  653
+
  654
+# If the value of the EXAMPLE_PATH tag contains directories, you can use the
  655
+# EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp
  656
+# and *.h) to filter out the source-files in the directories. If left
  657
+# blank all files are included.
  658
+
  659
+EXAMPLE_PATTERNS       =
  660
+
  661
+# If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be
  662
+# searched for input files to be used with the \include or \dontinclude
  663
+# commands irrespective of the value of the RECURSIVE tag.
  664
+# Possible values are YES and NO. If left blank NO is used.
  665
+
  666
+EXAMPLE_RECURSIVE      = NO
  667
+
  668
+# The IMAGE_PATH tag can be used to specify one or more files or
  669
+# directories that contain image that are included in the documentation (see
  670
+# the \image command).
  671
+
  672
+IMAGE_PATH             =
  673
+
  674
+# The INPUT_FILTER tag can be used to specify a program that doxygen should
  675
+# invoke to filter for each input file. Doxygen will invoke the filter program
  676
+# by executing (via popen()) the command <filter> <input-file>, where <filter>
  677
+# is the value of the INPUT_FILTER tag, and <input-file> is the name of an
  678
+# input file. Doxygen will then use the output that the filter program writes
  679
+# to standard output.
  680
+# If FILTER_PATTERNS is specified, this tag will be
  681
+# ignored.
  682
+
  683
+INPUT_FILTER           =
  684
+
  685
+# The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
  686
+# basis.
  687
+# Doxygen will compare the file name with each pattern and apply the
  688
+# filter if there is a match.
  689
+# The filters are a list of the form:
  690
+# pattern=filter (like *.cpp=my_cpp_filter). See INPUT_FILTER for further
  691
+# info on how filters are used. If FILTER_PATTERNS is empty or if
  692
+# non of the patterns match the file name, INPUT_FILTER is applied.
  693
+
  694
+FILTER_PATTERNS        =
  695
+
  696
+# If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using
  697
+# INPUT_FILTER) will be used to filter the input files when producing source
  698
+# files to browse (i.e. when SOURCE_BROWSER is set to YES).
  699
+
  700
+FILTER_SOURCE_FILES    = NO
  701
+
  702
+# The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file
  703
+# pattern. A pattern will override the setting for FILTER_PATTERN (if any)
  704
+# and it is also possible to disable source filtering for a specific pattern
  705
+# using *.ext= (so without naming a filter). This option only has effect when
  706
+# FILTER_SOURCE_FILES is enabled.
  707
+
  708
+FILTER_SOURCE_PATTERNS =
  709
+
  710
+#---------------------------------------------------------------------------
  711
+# configuration options related to source browsing
  712
+#---------------------------------------------------------------------------
  713
+
  714
+# If the SOURCE_BROWSER tag is set to YES then a list of source files will
  715
+# be generated. Documented entities will be cross-referenced with these sources.
  716
+# Note: To get rid of all source code in the generated output, make sure also
  717
+# VERBATIM_HEADERS is set to NO.
  718
+
  719
+SOURCE_BROWSER         = YES
  720
+
  721
+# Setting the INLINE_SOURCES tag to YES will include the body
  722
+# of functions and classes directly in the documentation.
  723
+
  724
+INLINE_SOURCES         = YES
  725
+
  726
+# Setting the STRIP_CODE_COMMENTS tag to YES (the default) will instruct
  727
+# doxygen to hide any special comment blocks from generated source code
  728
+# fragments. Normal C and C++ comments will always remain visible.
  729
+
  730
+STRIP_CODE_COMMENTS    = YES
  731
+
  732
+# If the REFERENCED_BY_RELATION tag is set to YES
  733
+# then for each documented function all documented
  734
+# functions referencing it will be listed.
  735
+
  736
+REFERENCED_BY_RELATION = YES
  737
+
  738
+# If the REFERENCES_RELATION tag is set to YES
  739
+# then for each documented function all documented entities
  740
+# called/used by that function will be listed.
  741
+
  742
+REFERENCES_RELATION    = NO
  743
+
  744
+# If the REFERENCES_LINK_SOURCE tag is set to YES (the default)
  745
+# and SOURCE_BROWSER tag is set to YES, then the hyperlinks from
  746
+# functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will
  747
+# link to the source code.
  748
+# Otherwise they will link to the documentation.
  749
+
  750
+REFERENCES_LINK_SOURCE = YES
  751
+
  752
+# If the USE_HTAGS tag is set to YES then the references to source code
  753
+# will point to the HTML generated by the htags(1) tool instead of doxygen
  754
+# built-in source browser. The htags tool is part of GNU's global source
  755
+# tagging system (see http://www.gnu.org/software/global/global.html). You
  756
+# will need version 4.8.6 or higher.
  757
+
  758
+USE_HTAGS              = NO
  759
+
  760
+# If the VERBATIM_HEADERS tag is set to YES (the default) then Doxygen
  761
+# will generate a verbatim copy of the header file for each class for
  762
+# which an include is specified. Set to NO to disable this.
  763
+
  764
+VERBATIM_HEADERS       = YES
  765
+
  766
+#---------------------------------------------------------------------------
  767
+# configuration options related to the alphabetical class index
  768
+#---------------------------------------------------------------------------
  769
+
  770
+# If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index
  771
+# of all compounds will be generated. Enable this if the project
  772
+# contains a lot of classes, structs, unions or interfaces.
  773
+
  774
+ALPHABETICAL_INDEX     = YES
  775
+
  776
+# If the alphabetical index is enabled (see ALPHABETICAL_INDEX) then
  777
+# the COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns
  778
+# in which this list will be split (can be a number in the range [1..20])
  779
+
  780
+COLS_IN_ALPHA_INDEX    = 5
  781
+
  782
+# In case all classes in a project start with a common prefix, all
  783
+# classes will be put under the same header in the alphabetical index.
  784
+# The IGNORE_PREFIX tag can be used to specify one or more prefixes that
  785
+# should be ignored while generating the index headers.
  786
+
  787
+IGNORE_PREFIX          =
  788
+
  789
+#---------------------------------------------------------------------------
  790
+# configuration options related to the HTML output
  791
+#---------------------------------------------------------------------------
  792
+
  793
+# If the GENERATE_HTML tag is set to YES (the default) Doxygen will
  794
+# generate HTML output.
  795
+
  796
+GENERATE_HTML          = YES
  797
+
  798
+# The HTML_OUTPUT tag is used to specify where the HTML docs will be put.
  799
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
  800
+# put in front of it. If left blank `html' will be used as the default path.
  801
+
  802
+HTML_OUTPUT            = html
  803
+
  804
+# The HTML_FILE_EXTENSION tag can be used to specify the file extension for
  805
+# each generated HTML page (for example: .htm,.php,.asp). If it is left blank
  806
+# doxygen will generate files with .html extension.
  807
+
  808
+HTML_FILE_EXTENSION    = .html
  809
+
  810
+# The HTML_HEADER tag can be used to specify a personal HTML header for
  811
+# each generated HTML page. If it is left blank doxygen will generate a
  812
+# standard header. Note that when using a custom header you are responsible
  813
+# for the proper inclusion of any scripts and style sheets that doxygen
  814
+# needs, which is dependent on the configuration options used.
  815
+# It is adviced to generate a default header using "doxygen -w html
  816
+# header.html footer.html stylesheet.css YourConfigFile" and then modify
  817
+# that header. Note that the header is subject to change so you typically
  818
+# have to redo this when upgrading to a newer version of doxygen or when changing the value of configuration settings such as GENERATE_TREEVIEW!
  819
+
  820
+HTML_HEADER            =
  821
+
  822
+# The HTML_FOOTER tag can be used to specify a personal HTML footer for
  823
+# each generated HTML page. If it is left blank doxygen will generate a
  824
+# standard footer.
  825
+
  826
+HTML_FOOTER            =
  827
+
  828
+# The HTML_STYLESHEET tag can be used to specify a user-defined cascading
  829
+# style sheet that is used by each HTML page. It can be used to
  830
+# fine-tune the look of the HTML output. If the tag is left blank doxygen
  831
+# will generate a default style sheet. Note that doxygen will try to copy
  832
+# the style sheet file to the HTML output directory, so don't put your own
  833
+# stylesheet in the HTML output directory as well, or it will be erased!
  834
+
  835
+HTML_STYLESHEET        =
  836
+
  837
+# The HTML_EXTRA_FILES tag can be used to specify one or more extra images or
  838
+# other source files which should be copied to the HTML output directory. Note
  839
+# that these files will be copied to the base HTML output directory. Use the
  840
+# $relpath$ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
  841
+# files. In the HTML_STYLESHEET file, use the file name only. Also note that
  842
+# the files will be copied as-is; there are no commands or markers available.
  843
+
  844
+HTML_EXTRA_FILES       =
  845
+
  846
+# The HTML_COLORSTYLE_HUE tag controls the color of the HTML output.
  847
+# Doxygen will adjust the colors in the stylesheet and background images
  848
+# according to this color. Hue is specified as an angle on a colorwheel,
  849
+# see http://en.wikipedia.org/wiki/Hue for more information.
  850
+# For instance the value 0 represents red, 60 is yellow, 120 is green,
  851
+# 180 is cyan, 240 is blue, 300 purple, and 360 is red again.
  852
+# The allowed range is 0 to 359.
  853
+
  854
+HTML_COLORSTYLE_HUE    = 220
  855
+
  856
+# The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of
  857
+# the colors in the HTML output. For a value of 0 the output will use
  858
+# grayscales only. A value of 255 will produce the most vivid colors.
  859
+
  860
+HTML_COLORSTYLE_SAT    = 100
  861
+
  862
+# The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to
  863
+# the luminance component of the colors in the HTML output. Values below
  864
+# 100 gradually make the output lighter, whereas values above 100 make
  865
+# the output darker. The value divided by 100 is the actual gamma applied,
  866
+# so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
  867
+# and 100 does not change the gamma.
  868
+
  869
+HTML_COLORSTYLE_GAMMA  = 80
  870
+
  871
+# If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML
  872
+# page will contain the date and time when the page was generated. Setting
  873
+# this to NO can help when comparing the output of multiple runs.
  874
+
  875
+HTML_TIMESTAMP         = YES
  876
+
  877
+# If the HTML_ALIGN_MEMBERS tag is set to YES, the members of classes,
  878
+# files or namespaces will be aligned in HTML using tables. If set to
  879
+# NO a bullet list will be used.
  880
+
  881
+HTML_ALIGN_MEMBERS     = YES
  882
+
  883
+# If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML
  884
+# documentation will contain sections that can be hidden and shown after the
  885
+# page has loaded. For this to work a browser that supports
  886
+# JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox
  887
+# Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari).
  888
+
  889
+HTML_DYNAMIC_SECTIONS  = NO
  890
+
  891
+# If the GENERATE_DOCSET tag is set to YES, additional index files
  892
+# will be generated that can be used as input for Apple's Xcode 3
  893
+# integrated development environment, introduced with OSX 10.5 (Leopard).
  894
+# To create a documentation set, doxygen will generate a Makefile in the
  895
+# HTML output directory. Running make will produce the docset in that
  896
+# directory and running "make install" will install the docset in
  897
+# ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find
  898
+# it at startup.
  899
+# See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html
  900
+# for more information.
  901
+
  902
+GENERATE_DOCSET        = NO
  903
+
  904
+# When GENERATE_DOCSET tag is set to YES, this tag determines the name of the
  905
+# feed. A documentation feed provides an umbrella under which multiple
  906
+# documentation sets from a single provider (such as a company or product suite)
  907
+# can be grouped.
  908
+
  909
+DOCSET_FEEDNAME        = "KISS Institute for Practical Robotics"
  910
+
  911
+# When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
  912
+# should uniquely identify the documentation set bundle. This should be a
  913
+# reverse domain-name style string, e.g. com.mycompany.MyDocSet. Doxygen
  914
+# will append .docset to the name.
  915
+
  916
+DOCSET_BUNDLE_ID       = org.doxygen.Project
  917
+
  918
+# When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
  919
+# the documentation publisher. This should be a reverse domain-name style
  920
+# string, e.g. com.mycompany.MyDocSet.documentation.
  921
+
  922
+DOCSET_PUBLISHER_ID    = org.doxygen.Publisher
  923
+
  924
+# The GENERATE_PUBLISHER_NAME tag identifies the documentation publisher.
  925
+
  926
+DOCSET_PUBLISHER_NAME  = Publisher
  927
+
  928
+# If the GENERATE_HTMLHELP tag is set to YES, additional index files
  929
+# will be generated that can be used as input for tools like the
  930
+# Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
  931
+# of the generated HTML documentation.
  932
+
  933
+GENERATE_HTMLHELP      = NO
  934
+
  935
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can
  936
+# be used to specify the file name of the resulting .chm file. You
  937
+# can add a path in front of the file if the result should not be
  938
+# written to the html output directory.
  939
+
  940
+CHM_FILE               =
  941
+
  942
+# If the GENERATE_HTMLHELP tag is set to YES, the HHC_LOCATION tag can
  943
+# be used to specify the location (absolute path including file name) of
  944
+# the HTML help compiler (hhc.exe). If non-empty doxygen will try to run
  945
+# the HTML help compiler on the generated index.hhp.
  946
+
  947
+HHC_LOCATION           =
  948
+
  949
+# If the GENERATE_HTMLHELP tag is set to YES, the GENERATE_CHI flag
  950
+# controls if a separate .chi index file is generated (YES) or that
  951
+# it should be included in the master .chm file (NO).
  952
+
  953
+GENERATE_CHI           = NO
  954
+
  955
+# If the GENERATE_HTMLHELP tag is set to YES, the CHM_INDEX_ENCODING
  956
+# is used to encode HtmlHelp index (hhk), content (hhc) and project file
  957
+# content.
  958
+
  959
+CHM_INDEX_ENCODING     =
  960
+
  961
+# If the GENERATE_HTMLHELP tag is set to YES, the BINARY_TOC flag
  962
+# controls whether a binary table of contents is generated (YES) or a
  963
+# normal table of contents (NO) in the .chm file.
  964
+
  965
+BINARY_TOC             = NO
  966
+
  967
+# The TOC_EXPAND flag can be set to YES to add extra items for group members
  968
+# to the contents of the HTML help documentation and to the tree view.
  969
+
  970
+TOC_EXPAND             = NO
  971
+
  972
+# If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and
  973
+# QHP_VIRTUAL_FOLDER are set, an additional index file will be generated
  974
+# that can be used as input for Qt's qhelpgenerator to generate a
  975
+# Qt Compressed Help (.qch) of the generated HTML documentation.
  976
+
  977
+GENERATE_QHP           = NO
  978
+
  979
+# If the QHG_LOCATION tag is specified, the QCH_FILE tag can
  980
+# be used to specify the file name of the resulting .qch file.
  981
+# The path specified is relative to the HTML output folder.
  982
+
  983
+QCH_FILE               =
  984
+
  985
+# The QHP_NAMESPACE tag specifies the namespace to use when generating
  986
+# Qt Help Project output. For more information please see
  987
+# http://doc.trolltech.com/qthelpproject.html#namespace
  988
+
  989
+QHP_NAMESPACE          = org.doxygen.Project
  990
+
  991
+# The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating
  992
+# Qt Help Project output. For more information please see
  993
+# http://doc.trolltech.com/qthelpproject.html#virtual-folders
  994
+
  995
+QHP_VIRTUAL_FOLDER     = doc
  996
+
  997
+# If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
  998
+# add. For more information please see
  999
+# http://doc.trolltech.com/qthelpproject.html#custom-filters
  1000
+
  1001
+QHP_CUST_FILTER_NAME   =
  1002
+
  1003
+# The QHP_CUST_FILT_ATTRS tag specifies the list of the attributes of the
  1004
+# custom filter to add. For more information please see
  1005
+# <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
  1006
+# Qt Help Project / Custom Filters</a>.
  1007
+
  1008
+QHP_CUST_FILTER_ATTRS  =
  1009
+
  1010
+# The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this
  1011
+# project's
  1012
+# filter section matches.
  1013
+# <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
  1014
+# Qt Help Project / Filter Attributes</a>.
  1015
+
  1016
+QHP_SECT_FILTER_ATTRS  =
  1017
+
  1018
+# If the GENERATE_QHP tag is set to YES, the QHG_LOCATION tag can
  1019
+# be used to specify the location of Qt's qhelpgenerator.
  1020
+# If non-empty doxygen will try to run qhelpgenerator on the generated
  1021
+# .qhp file.
  1022
+
  1023
+QHG_LOCATION           =
  1024
+
  1025
+# If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files
  1026
+#  will be generated, which together with the HTML files, form an Eclipse help
  1027
+# plugin. To install this plugin and make it available under the help contents
  1028
+# menu in Eclipse, the contents of the directory containing the HTML and XML
  1029
+# files needs to be copied into the plugins directory of eclipse. The name of
  1030
+# the directory within the plugins directory should be the same as
  1031
+# the ECLIPSE_DOC_ID value. After copying Eclipse needs to be restarted before
  1032
+# the help appears.
  1033
+
  1034
+GENERATE_ECLIPSEHELP   = NO
  1035
+
  1036
+# A unique identifier for the eclipse help plugin. When installing the plugin
  1037
+# the directory name containing the HTML and XML files should also have
  1038
+# this name.
  1039
+
  1040
+ECLIPSE_DOC_ID         = org.doxygen.Project
  1041
+
  1042
+# The DISABLE_INDEX tag can be used to turn on/off the condensed index at
  1043
+# top of each HTML page. The value NO (the default) enables the index and
  1044
+# the value YES disables it.
  1045
+
  1046
+DISABLE_INDEX          = NO
  1047
+
  1048
+# The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values
  1049
+# (range [0,1..20]) that doxygen will group on one line in the generated HTML
  1050
+# documentation. Note that a value of 0 will completely suppress the enum
  1051
+# values from appearing in the overview section.
  1052
+
  1053
+ENUM_VALUES_PER_LINE   = 4
  1054
+
  1055
+# The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
  1056
+# structure should be generated to display hierarchical information.
  1057
+# If the tag value is set to YES, a side panel will be generated
  1058
+# containing a tree-like index structure (just like the one that
  1059
+# is generated for HTML Help). For this to work a browser that supports
  1060
+# JavaScript, DHTML, CSS and frames is required (i.e. any modern browser).
  1061
+# Windows users are probably better off using the HTML help feature.
  1062
+
  1063
+GENERATE_TREEVIEW      = NO
  1064
+
  1065
+# By enabling USE_INLINE_TREES, doxygen will generate the Groups, Directories,
  1066
+# and Class Hierarchy pages using a tree view instead of an ordered list.
  1067
+
  1068
+USE_INLINE_TREES       = NO
  1069
+
  1070
+# If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be
  1071
+# used to set the initial width (in pixels) of the frame in which the tree
  1072
+# is shown.
  1073
+
  1074
+TREEVIEW_WIDTH         = 250
  1075
+
  1076
+# When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open
  1077
+# links to external symbols imported via tag files in a separate window.
  1078
+
  1079
+EXT_LINKS_IN_WINDOW    = NO
  1080
+
  1081
+# Use this tag to change the font size of Latex formulas included
  1082
+# as images in the HTML documentation. The default is 10. Note that
  1083
+# when you change the font size after a successful doxygen run you need
  1084
+# to manually remove any form_*.png images from the HTML output directory
  1085
+# to force them to be regenerated.
  1086
+
  1087
+FORMULA_FONTSIZE       = 10
  1088
+
  1089
+# Use the FORMULA_TRANPARENT tag to determine whether or not the images
  1090
+# generated for formulas are transparent PNGs. Transparent PNGs are
  1091
+# not supported properly for IE 6.0, but are supported on all modern browsers.
  1092
+# Note that when changing this option you need to delete any form_*.png files
  1093
+# in the HTML output before the changes have effect.
  1094
+
  1095
+FORMULA_TRANSPARENT    = YES
  1096
+
  1097
+# Enable the USE_MATHJAX option to render LaTeX formulas using MathJax
  1098
+# (see http://www.mathjax.org) which uses client side Javascript for the
  1099
+# rendering instead of using prerendered bitmaps. Use this if you do not
  1100
+# have LaTeX installed or if you want to formulas look prettier in the HTML
  1101
+# output. When enabled you also need to install MathJax separately and
  1102
+# configure the path to it using the MATHJAX_RELPATH option.
  1103
+
  1104
+USE_MATHJAX            = NO
  1105
+
  1106
+# When MathJax is enabled you need to specify the location relative to the
  1107
+# HTML output directory using the MATHJAX_RELPATH option. The destination
  1108
+# directory should contain the MathJax.js script. For instance, if the mathjax
  1109
+# directory is located at the same level as the HTML output directory, then
  1110
+# MATHJAX_RELPATH should be ../mathjax. The default value points to the
  1111
+# mathjax.org site, so you can quickly see the result without installing
  1112
+# MathJax, but it is strongly recommended to install a local copy of MathJax
  1113
+# before deployment.
  1114
+
  1115
+MATHJAX_RELPATH        = http://www.mathjax.org/mathjax
  1116
+
  1117
+# When the SEARCHENGINE tag is enabled doxygen will generate a search box
  1118
+# for the HTML output. The underlying search engine uses javascript
  1119
+# and DHTML and should work on any modern browser. Note that when using
  1120
+# HTML help (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets
  1121
+# (GENERATE_DOCSET) there is already a search function so this one should
  1122
+# typically be disabled. For large projects the javascript based search engine
  1123
+# can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
  1124
+
  1125
+SEARCHENGINE           = YES
  1126
+
  1127
+# When the SERVER_BASED_SEARCH tag is enabled the search engine will be
  1128
+# implemented using a PHP enabled web server instead of at the web client
  1129
+# using Javascript. Doxygen will generate the search PHP script and index
  1130
+# file to put on the web server. The advantage of the server
  1131
+# based approach is that it scales better to large projects and allows
  1132
+# full text search. The disadvantages are that it is more difficult to setup
  1133
+# and does not have live searching capabilities.
  1134
+
  1135
+SERVER_BASED_SEARCH    = NO
  1136
+
  1137
+#---------------------------------------------------------------------------
  1138
+# configuration options related to the LaTeX output
  1139
+#---------------------------------------------------------------------------
  1140
+
  1141
+# If the GENERATE_LATEX tag is set to YES (the default) Doxygen will
  1142
+# generate Latex output.
  1143
+
  1144
+GENERATE_LATEX         = YES
  1145
+
  1146
+# The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put.
  1147
+# If a relative path is entered the value of OUTPUT_DIRECTORY will be
  1148
+# put in front of it. If left blank `latex' will be used as the default path.
  1149
+
  1150
+LATEX_OUTPUT           = latex
  1151
+
  1152
+# The LATEX_CMD_NAME tag can be used to specify the LaTeX command name to be
  1153
+# invoked. If left blank `latex' will be used as the default command name.
  1154
+# Note that when enabling USE_PDFLATEX this option is only used for
  1155
+# generating bitmaps for formulas in the HTML output, but not in the
  1156
+# Makefile that is written to the output directory.
  1157
+
  1158
+LATEX_CMD_NAME         = latex
  1159
+
  1160
+# The MAKEINDEX_CMD_NAME tag can be used to specify the command name to
  1161
+# generate index for LaTeX. If left blank `makeindex' will be used as the
  1162
+# default command name.
  1163
+
  1164
+MAKEINDEX_CMD_NAME     = makeindex
  1165
+
  1166
+# If the COMPACT_LATEX tag is set to YES Doxygen generates more compact
  1167
+# LaTeX documents. This may be useful for small projects and may help to
  1168
+# save some trees in general.
  1169
+
  1170
+COMPACT_LATEX          = NO
  1171
+
  1172
+# The PAPER_TYPE tag can be used to set the paper type that is used
  1173
+# by the printer. Possible values are: a4, letter, legal and
  1174
+# executive. If left blank a4wide will be used.
  1175
+
  1176
+PAPER_TYPE             = a4
  1177
+
  1178
+# The EXTRA_PACKAGES tag can be to specify one or more names of LaTeX
  1179
+# packages that should be included in the LaTeX output.
  1180
+
  1181
+EXTRA_PACKAGES         =
  1182
+
  1183
+# The LATEX_HEADER tag can be used to specify a personal LaTeX header for
  1184
+# the generated latex document. The header should contain everything until
  1185
+# the first chapter. If it is left blank doxygen will generate a
  1186
+# standard header. Notice: only use this tag if you know what you are doing!
  1187
+
  1188
+LATEX_HEADER           =
  1189
+
  1190
+# The LATEX_FOOTER tag can be used to specify a personal LaTeX footer for
  1191
+# the generated latex document. The footer should contain everything after
  1192
+# the last chapter. If it is left blank doxygen will generate a
  1193
+# standard footer. Notice: only use this tag if you know what you are doing!