├── .gitignore ├── README.md ├── doxygen ├── doxygen.exe ├── generate.bat ├── logo.png ├── manual ├── manual.css ├── manual.html └── manual.xml ├── res └── Images │ ├── mainpage.gif │ ├── plugin-1.jpg │ ├── plugin-manage-1.jpg │ ├── summary-1.jpg │ └── temp │ ├── 1-1.jpg │ ├── 2-1-1.jpg │ ├── 2-1-2.jpg │ ├── 2-1-3.jpg │ ├── 2-2-1.jpg │ ├── 2-2-2.jpg │ ├── 2-2-3.jpg │ ├── 2-2-4.jpg │ ├── 2-2-5.jpg │ ├── 2-3-1.jpg │ ├── 2-3-2.jpg │ ├── 2-4-1.jpg │ ├── 2-4-2.jpg │ ├── 3-1-1-1.jpg │ ├── 3-1-1-2.jpg │ ├── 3-1-1.jpg │ ├── 3-1-2-1-1-1.jpg │ ├── 3-1-2-1-1-2.jpg │ ├── 3-1-2-1-1-3.jpg │ ├── 3-1-2-1-1.jpg │ ├── 3-1-2-1-2-1.jpg │ ├── 3-1-2-1-2-2.jpg │ ├── 3-1-2-1-2.jpg │ ├── 3-1-2-1-3.jpg │ ├── 3-1-2-1-4.jpg │ ├── 3-1-2-1-5.jpg │ ├── 3-1-2-1-6.jpg │ ├── 3-1-2-1.jpg │ ├── 3-1-2-2-1.jpg │ ├── 3-1-2-2-2.jpg │ ├── 3-1-2-2.jpg │ ├── 3-1-2-3.jpg │ ├── 3-2-1-1.jpg │ ├── 3-2-1.jpg │ ├── 3-2-2-2.jpg │ ├── 3-2-2-3.jpg │ ├── 3-2-2-4.jpg │ ├── 3-2-3-1.jpg │ ├── 3-2-4-1.jpg │ ├── 3-2-5-1.jpg │ ├── 3-2-6-1.jpg │ ├── 3-2-7-1.jpg │ ├── 4-1.jpg │ ├── 4-2.jpg │ ├── 4-3.jpg │ ├── 5-1-1.jpg │ ├── 5-1-2.jpg │ ├── 5-1-3.jpg │ ├── 5-10-1.jpg │ ├── 5-10-10.jpg │ ├── 5-10-11.jpg │ ├── 5-10-2.jpg │ ├── 5-10-3.jpg │ ├── 5-10-4.jpg │ ├── 5-10-5.jpg │ ├── 5-10-6.jpg │ ├── 5-10-7.jpg │ ├── 5-10-8.jpg │ ├── 5-10-9.jpg │ ├── 5-2-1-1.jpg │ ├── 5-2-1-2.jpg │ ├── 5-2-1-3.jpg │ ├── 5-2-1-4.jpg │ ├── 5-2-1-5.jpg │ ├── 5-2-1-6.jpg │ ├── 5-2-1.jpg │ ├── 5-2-2-1.jpg │ ├── 5-2-2-2.jpg │ ├── 5-2-2-3.jpg │ ├── 5-2-2-4.jpg │ ├── 5-2-2.jpg │ ├── 5-2-3-1.jpg │ ├── 5-2-3.jpg │ ├── 5-3-1-1.jpg │ ├── 5-3-2-1-1.jpg │ ├── 5-3-2-1-2.jpg │ ├── 5-3-2-1.jpg │ ├── 5-3-5-1.jpg │ ├── 5-3-5-2.jpg │ ├── 5-4-1.jpg │ ├── 5-5-1.jpg │ ├── 5-5-2.jpg │ ├── 5-5-3.jpg │ ├── 5-5-4.jpg │ ├── 5-5-5.jpg │ ├── 5-5-6.jpg │ ├── 5-5-7.jpg │ ├── 5-5-8.jpg │ ├── 5-6-1.jpg │ ├── 5-6-2.jpg │ ├── 5-6-3.jpg │ ├── 5-7-1.jpg │ ├── 5-7-2.jpg │ ├── 5-7-3.jpg │ ├── 5-7-4.jpg │ ├── 5-7-5.jpg │ ├── 5-8-1.jpg │ ├── 5-8-2.jpg │ ├── 5-8-3.jpg │ ├── 5-9-1.jpg │ └── 5-9-2.jpg └── src ├── 1-summary.md ├── 2-launcher.md ├── 3-plugin.md ├── 4-preference.md ├── 5-faq.md ├── home.md ├── plugin ├── bangumi.md ├── cardinal-system.md ├── ggo-theme.md ├── ggo-widget.md ├── hp-bar.md ├── image-widget.md ├── mail-box.md ├── music-player-support.md ├── pdh-data-extension.md ├── quick-launch.md ├── sensor-data-extension.md ├── shortcut-keys-extension.md ├── weather-data-extension.md ├── web-browser-engine.md └── web-widget.md ├── x-bug.md ├── x-history.md └── x-misc.md /.gitignore: -------------------------------------------------------------------------------- 1 | 2 | # ignore files 3 | 4 | /output 5 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # NERvManual 2 | Nerve Gear Manual - SAO Utils 用户指南 3 | 4 | ## 注意 5 | 6 | 提交前请先运行 ./doxygen/generate.bat 生成并审阅测试文档 ./output/manual.chs/index.html 7 | 8 | > 教程文档将在提交后 5 分钟内自动生成, 地址: http://nvg.gpbeta.com/manual/ 9 | 10 | ## 规范 11 | 12 | 1. 能用 Markdown 语法的尽量不要用 HTML 标记 13 | -------------------------------------------------------------------------------- /doxygen/doxygen.exe: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/NERvGear/NERvManual/749330a97a1c996017625212ad118a3332e4cc7c/doxygen/doxygen.exe -------------------------------------------------------------------------------- /doxygen/generate.bat: -------------------------------------------------------------------------------- 1 | 2 | doxygen.exe manual 3 | 4 | PAUSE -------------------------------------------------------------------------------- /doxygen/logo.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/NERvGear/NERvManual/749330a97a1c996017625212ad118a3332e4cc7c/doxygen/logo.png -------------------------------------------------------------------------------- /doxygen/manual: -------------------------------------------------------------------------------- 1 | # Doxyfile 1.8.8 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 double hash (##) is considered a comment and is placed in 7 | # front of the TAG it is preceding. 8 | # 9 | # All text after a single hash (#) is considered a comment and will be ignored. 10 | # The format is: 11 | # TAG = value [value, ...] 12 | # For lists, items can also be appended using: 13 | # TAG += value [value, ...] 14 | # Values that contain spaces should be placed between quotes (\" \"). 15 | 16 | #--------------------------------------------------------------------------- 17 | # Project related configuration options 18 | #--------------------------------------------------------------------------- 19 | 20 | # This tag specifies the encoding used for all characters in the config file 21 | # that follow. The default is UTF-8 which is also the encoding used for all text 22 | # before the first occurrence of this tag. Doxygen uses libiconv (or the iconv 23 | # built into libc) for the transcoding. See http://www.gnu.org/software/libiconv 24 | # for the list of possible encodings. 25 | # The default value is: UTF-8. 26 | 27 | DOXYFILE_ENCODING = UTF-8 28 | 29 | # The PROJECT_NAME tag is a single word (or a sequence of words surrounded by 30 | # double-quotes, unless you are using Doxywizard) that should identify the 31 | # project for which the documentation is generated. This name is used in the 32 | # title of most generated pages and in a few other places. 33 | # The default value is: My Project. 34 | 35 | PROJECT_NAME = "SAO Utils 用户指南" 36 | 37 | # The PROJECT_NUMBER tag can be used to enter a project or revision number. This 38 | # could be handy for archiving the generated documentation or if some version 39 | # control system is used. 40 | 41 | PROJECT_NUMBER = 0.3.1 42 | 43 | # Using the PROJECT_BRIEF tag one can provide an optional one line description 44 | # for a project that appears at the top of each page and should give viewer a 45 | # quick idea about the purpose of the project. Keep the description short. 46 | 47 | PROJECT_BRIEF = "NERvManual - SAO Utils 快速入门教程" 48 | 49 | # With the PROJECT_LOGO tag one can specify an logo or icon that is included in 50 | # the documentation. The maximum height of the logo should not exceed 55 pixels 51 | # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo 52 | # to the output directory. 53 | 54 | PROJECT_LOGO = logo.png 55 | 56 | # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) path 57 | # into which the generated documentation will be written. If a relative path is 58 | # entered, it will be relative to the location where doxygen was started. If 59 | # left blank the current directory will be used. 60 | 61 | OUTPUT_DIRECTORY = "../output" 62 | 63 | # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub- 64 | # directories (in 2 levels) under the output directory of each output format and 65 | # will distribute the generated files over these directories. Enabling this 66 | # option can be useful when feeding doxygen a huge amount of source files, where 67 | # putting all generated files in the same directory would otherwise causes 68 | # performance problems for the file system. 69 | # The default value is: NO. 70 | 71 | CREATE_SUBDIRS = NO 72 | 73 | # If the ALLOW_UNICODE_NAMES tag is set to YES, doxygen will allow non-ASCII 74 | # characters to appear in the names of generated files. If set to NO, non-ASCII 75 | # characters will be escaped, for example _xE3_x81_x84 will be used for Unicode 76 | # U+3044. 77 | # The default value is: NO. 78 | 79 | ALLOW_UNICODE_NAMES = NO 80 | 81 | # The OUTPUT_LANGUAGE tag is used to specify the language in which all 82 | # documentation generated by doxygen is written. Doxygen will use this 83 | # information to generate all constant output in the proper language. 84 | # Possible values are: Afrikaans, Arabic, Armenian, Brazilian, Catalan, Chinese, 85 | # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States), 86 | # Esperanto, Farsi (Persian), Finnish, French, German, Greek, Hungarian, 87 | # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages), 88 | # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian, 89 | # Macedonian, Norwegian, Persian (Farsi), Polish, Portuguese, Romanian, Russian, 90 | # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish, 91 | # Ukrainian and Vietnamese. 92 | # The default value is: English. 93 | 94 | OUTPUT_LANGUAGE = Chinese 95 | 96 | # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member 97 | # descriptions after the members that are listed in the file and class 98 | # documentation (similar to Javadoc). Set to NO to disable this. 99 | # The default value is: YES. 100 | 101 | BRIEF_MEMBER_DESC = YES 102 | 103 | # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief 104 | # description of a member or function before the detailed description 105 | # 106 | # Note: If both HIDE_UNDOC_MEMBERS and BRIEF_MEMBER_DESC are set to NO, the 107 | # brief descriptions will be completely suppressed. 108 | # The default value is: YES. 109 | 110 | REPEAT_BRIEF = YES 111 | 112 | # This tag implements a quasi-intelligent brief description abbreviator that is 113 | # used to form the text in various listings. Each string in this list, if found 114 | # as the leading text of the brief description, will be stripped from the text 115 | # and the result, after processing the whole list, is used as the annotated 116 | # text. Otherwise, the brief description is used as-is. If left blank, the 117 | # following values are used ($name is automatically replaced with the name of 118 | # the entity):The $name class, The $name widget, The $name file, is, provides, 119 | # specifies, contains, represents, a, an and the. 120 | 121 | ABBREVIATE_BRIEF = "The $name class" \ 122 | "The $name widget" \ 123 | "The $name file" \ 124 | is \ 125 | provides \ 126 | specifies \ 127 | contains \ 128 | represents \ 129 | a \ 130 | an \ 131 | the 132 | 133 | # If the ALWAYS_DETAILED_SEC and REPEAT_BRIEF tags are both set to YES then 134 | # doxygen will generate a detailed section even if there is only a brief 135 | # description. 136 | # The default value is: NO. 137 | 138 | ALWAYS_DETAILED_SEC = NO 139 | 140 | # If the INLINE_INHERITED_MEMB tag is set to YES, doxygen will show all 141 | # inherited members of a class in the documentation of that class as if those 142 | # members were ordinary class members. Constructors, destructors and assignment 143 | # operators of the base classes will not be shown. 144 | # The default value is: NO. 145 | 146 | INLINE_INHERITED_MEMB = NO 147 | 148 | # If the FULL_PATH_NAMES tag is set to YES doxygen will prepend the full path 149 | # before files name in the file list and in the header files. If set to NO the 150 | # shortest path that makes the file name unique will be used 151 | # The default value is: YES. 152 | 153 | FULL_PATH_NAMES = YES 154 | 155 | # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path. 156 | # Stripping is only done if one of the specified strings matches the left-hand 157 | # part of the path. The tag can be used to show relative paths in the file list. 158 | # If left blank the directory from which doxygen is run is used as the path to 159 | # strip. 160 | # 161 | # Note that you can specify absolute paths here, but also relative paths, which 162 | # will be relative from the directory where doxygen is started. 163 | # This tag requires that the tag FULL_PATH_NAMES is set to YES. 164 | 165 | STRIP_FROM_PATH = 166 | 167 | # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the 168 | # path mentioned in the documentation of a class, which tells the reader which 169 | # header file to include in order to use a class. If left blank only the name of 170 | # the header file containing the class definition is used. Otherwise one should 171 | # specify the list of include paths that are normally passed to the compiler 172 | # using the -I flag. 173 | 174 | STRIP_FROM_INC_PATH = 175 | 176 | # If the SHORT_NAMES tag is set to YES, doxygen will generate much shorter (but 177 | # less readable) file names. This can be useful is your file systems doesn't 178 | # support long names like on DOS, Mac, or CD-ROM. 179 | # The default value is: NO. 180 | 181 | SHORT_NAMES = NO 182 | 183 | # If the JAVADOC_AUTOBRIEF tag is set to YES then doxygen will interpret the 184 | # first line (until the first dot) of a Javadoc-style comment as the brief 185 | # description. If set to NO, the Javadoc-style will behave just like regular Qt- 186 | # style comments (thus requiring an explicit @brief command for a brief 187 | # description.) 188 | # The default value is: NO. 189 | 190 | JAVADOC_AUTOBRIEF = NO 191 | 192 | # If the QT_AUTOBRIEF tag is set to YES then doxygen will interpret the first 193 | # line (until the first dot) of a Qt-style comment as the brief description. If 194 | # set to NO, the Qt-style will behave just like regular Qt-style comments (thus 195 | # requiring an explicit \brief command for a brief description.) 196 | # The default value is: NO. 197 | 198 | QT_AUTOBRIEF = NO 199 | 200 | # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make doxygen treat a 201 | # multi-line C++ special comment block (i.e. a block of //! or /// comments) as 202 | # a brief description. This used to be the default behavior. The new default is 203 | # to treat a multi-line C++ comment block as a detailed description. Set this 204 | # tag to YES if you prefer the old behavior instead. 205 | # 206 | # Note that setting this tag to YES also means that rational rose comments are 207 | # not recognized any more. 208 | # The default value is: NO. 209 | 210 | MULTILINE_CPP_IS_BRIEF = YES 211 | 212 | # If the INHERIT_DOCS tag is set to YES then an undocumented member inherits the 213 | # documentation from any documented member that it re-implements. 214 | # The default value is: YES. 215 | 216 | INHERIT_DOCS = YES 217 | 218 | # If the SEPARATE_MEMBER_PAGES tag is set to YES, then doxygen will produce a 219 | # new page for each member. If set to NO, the documentation of a member will be 220 | # part of the file/class/namespace that contains it. 221 | # The default value is: NO. 222 | 223 | SEPARATE_MEMBER_PAGES = NO 224 | 225 | # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen 226 | # uses this value to replace tabs by spaces in code fragments. 227 | # Minimum value: 1, maximum value: 16, default value: 4. 228 | 229 | TAB_SIZE = 4 230 | 231 | # This tag can be used to specify a number of aliases that act as commands in 232 | # the documentation. An alias has the form: 233 | # name=value 234 | # For example adding 235 | # "sideeffect=@par Side Effects:\n" 236 | # will allow you to put the command \sideeffect (or @sideeffect) in the 237 | # documentation, which will result in a user-defined paragraph with heading 238 | # "Side Effects:". You can put \n's in the value part of an alias to insert 239 | # newlines. 240 | 241 | ALIASES = 242 | 243 | # This tag can be used to specify a number of word-keyword mappings (TCL only). 244 | # A mapping has the form "name=value". For example adding "class=itcl::class" 245 | # will allow you to use the command class in the itcl::class meaning. 246 | 247 | TCL_SUBST = 248 | 249 | # Set the OPTIMIZE_OUTPUT_FOR_C tag to YES if your project consists of C sources 250 | # only. Doxygen will then generate output that is more tailored for C. For 251 | # instance, some of the names that are used will be different. The list of all 252 | # members will be omitted, etc. 253 | # The default value is: NO. 254 | 255 | OPTIMIZE_OUTPUT_FOR_C = NO 256 | 257 | # Set the OPTIMIZE_OUTPUT_JAVA tag to YES if your project consists of Java or 258 | # Python sources only. Doxygen will then generate output that is more tailored 259 | # for that language. For instance, namespaces will be presented as packages, 260 | # qualified scopes will look different, etc. 261 | # The default value is: NO. 262 | 263 | OPTIMIZE_OUTPUT_JAVA = NO 264 | 265 | # Set the OPTIMIZE_FOR_FORTRAN tag to YES if your project consists of Fortran 266 | # sources. Doxygen will then generate output that is tailored for Fortran. 267 | # The default value is: NO. 268 | 269 | OPTIMIZE_FOR_FORTRAN = NO 270 | 271 | # Set the OPTIMIZE_OUTPUT_VHDL tag to YES if your project consists of VHDL 272 | # sources. Doxygen will then generate output that is tailored for VHDL. 273 | # The default value is: NO. 274 | 275 | OPTIMIZE_OUTPUT_VHDL = NO 276 | 277 | # Doxygen selects the parser to use depending on the extension of the files it 278 | # parses. With this tag you can assign which parser to use for a given 279 | # extension. Doxygen has a built-in mapping, but you can override or extend it 280 | # using this tag. The format is ext=language, where ext is a file extension, and 281 | # language is one of the parsers supported by doxygen: IDL, Java, Javascript, 282 | # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran: 283 | # FortranFixed, free formatted Fortran: FortranFree, unknown formatted Fortran: 284 | # Fortran. In the later case the parser tries to guess whether the code is fixed 285 | # or free formatted code, this is the default for Fortran type files), VHDL. For 286 | # instance to make doxygen treat .inc files as Fortran files (default is PHP), 287 | # and .f files as C (default is Fortran), use: inc=Fortran f=C. 288 | # 289 | # Note For files without extension you can use no_extension as a placeholder. 290 | # 291 | # Note that for custom extensions you also need to set FILE_PATTERNS otherwise 292 | # the files are not read by doxygen. 293 | 294 | EXTENSION_MAPPING = 295 | 296 | # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments 297 | # according to the Markdown format, which allows for more readable 298 | # documentation. See http://daringfireball.net/projects/markdown/ for details. 299 | # The output of markdown processing is further processed by doxygen, so you can 300 | # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in 301 | # case of backward compatibilities issues. 302 | # The default value is: YES. 303 | 304 | MARKDOWN_SUPPORT = YES 305 | 306 | # When enabled doxygen tries to link words that correspond to documented 307 | # classes, or namespaces to their corresponding documentation. Such a link can 308 | # be prevented in individual cases by by putting a % sign in front of the word 309 | # or globally by setting AUTOLINK_SUPPORT to NO. 310 | # The default value is: YES. 311 | 312 | AUTOLINK_SUPPORT = YES 313 | 314 | # If you use STL classes (i.e. std::string, std::vector, etc.) but do not want 315 | # to include (a tag file for) the STL sources as input, then you should set this 316 | # tag to YES in order to let doxygen match functions declarations and 317 | # definitions whose arguments contain STL classes (e.g. func(std::string); 318 | # versus func(std::string) {}). This also make the inheritance and collaboration 319 | # diagrams that involve STL classes more complete and accurate. 320 | # The default value is: NO. 321 | 322 | BUILTIN_STL_SUPPORT = NO 323 | 324 | # If you use Microsoft's C++/CLI language, you should set this option to YES to 325 | # enable parsing support. 326 | # The default value is: NO. 327 | 328 | CPP_CLI_SUPPORT = NO 329 | 330 | # Set the SIP_SUPPORT tag to YES if your project consists of sip (see: 331 | # http://www.riverbankcomputing.co.uk/software/sip/intro) sources only. Doxygen 332 | # will parse them like normal C++ but will assume all classes use public instead 333 | # of private inheritance when no explicit protection keyword is present. 334 | # The default value is: NO. 335 | 336 | SIP_SUPPORT = NO 337 | 338 | # For Microsoft's IDL there are propget and propput attributes to indicate 339 | # getter and setter methods for a property. Setting this option to YES will make 340 | # doxygen to replace the get and set methods by a property in the documentation. 341 | # This will only work if the methods are indeed getting or setting a simple 342 | # type. If this is not the case, or you want to show the methods anyway, you 343 | # should set this option to NO. 344 | # The default value is: YES. 345 | 346 | IDL_PROPERTY_SUPPORT = YES 347 | 348 | # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 349 | # tag is set to YES, then doxygen will reuse the documentation of the first 350 | # member in the group (if any) for the other members of the group. By default 351 | # all members of a group must be documented explicitly. 352 | # The default value is: NO. 353 | 354 | DISTRIBUTE_GROUP_DOC = NO 355 | 356 | # Set the SUBGROUPING tag to YES to allow class member groups of the same type 357 | # (for instance a group of public functions) to be put as a subgroup of that 358 | # type (e.g. under the Public Functions section). Set it to NO to prevent 359 | # subgrouping. Alternatively, this can be done per class using the 360 | # \nosubgrouping command. 361 | # The default value is: YES. 362 | 363 | SUBGROUPING = YES 364 | 365 | # When the INLINE_GROUPED_CLASSES tag is set to YES, classes, structs and unions 366 | # are shown inside the group in which they are included (e.g. using \ingroup) 367 | # instead of on a separate page (for HTML and Man pages) or section (for LaTeX 368 | # and RTF). 369 | # 370 | # Note that this feature does not work in combination with 371 | # SEPARATE_MEMBER_PAGES. 372 | # The default value is: NO. 373 | 374 | INLINE_GROUPED_CLASSES = NO 375 | 376 | # When the INLINE_SIMPLE_STRUCTS tag is set to YES, structs, classes, and unions 377 | # with only public data fields or simple typedef fields will be shown inline in 378 | # the documentation of the scope in which they are defined (i.e. file, 379 | # namespace, or group documentation), provided this scope is documented. If set 380 | # to NO, structs, classes, and unions are shown on a separate page (for HTML and 381 | # Man pages) or section (for LaTeX and RTF). 382 | # The default value is: NO. 383 | 384 | INLINE_SIMPLE_STRUCTS = NO 385 | 386 | # When TYPEDEF_HIDES_STRUCT tag is enabled, a typedef of a struct, union, or 387 | # enum is documented as struct, union, or enum with the name of the typedef. So 388 | # typedef struct TypeS {} TypeT, will appear in the documentation as a struct 389 | # with name TypeT. When disabled the typedef will appear as a member of a file, 390 | # namespace, or class. And the struct will be named TypeS. This can typically be 391 | # useful for C code in case the coding convention dictates that all compound 392 | # types are typedef'ed and only the typedef is referenced, never the tag name. 393 | # The default value is: NO. 394 | 395 | TYPEDEF_HIDES_STRUCT = NO 396 | 397 | # The size of the symbol lookup cache can be set using LOOKUP_CACHE_SIZE. This 398 | # cache is used to resolve symbols given their name and scope. Since this can be 399 | # an expensive process and often the same symbol appears multiple times in the 400 | # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small 401 | # doxygen will become slower. If the cache is too large, memory is wasted. The 402 | # cache size is given by this formula: 2^(16+LOOKUP_CACHE_SIZE). The valid range 403 | # is 0..9, the default is 0, corresponding to a cache size of 2^16=65536 404 | # symbols. At the end of a run doxygen will report the cache usage and suggest 405 | # the optimal cache size from a speed point of view. 406 | # Minimum value: 0, maximum value: 9, default value: 0. 407 | 408 | LOOKUP_CACHE_SIZE = 0 409 | 410 | #--------------------------------------------------------------------------- 411 | # Build related configuration options 412 | #--------------------------------------------------------------------------- 413 | 414 | # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in 415 | # documentation are documented, even if no documentation was available. Private 416 | # class members and static file members will be hidden unless the 417 | # EXTRACT_PRIVATE respectively EXTRACT_STATIC tags are set to YES. 418 | # Note: This will also disable the warnings about undocumented members that are 419 | # normally produced when WARNINGS is set to YES. 420 | # The default value is: NO. 421 | 422 | EXTRACT_ALL = NO 423 | 424 | # If the EXTRACT_PRIVATE tag is set to YES all private members of a class will 425 | # be included in the documentation. 426 | # The default value is: NO. 427 | 428 | EXTRACT_PRIVATE = NO 429 | 430 | # If the EXTRACT_PACKAGE tag is set to YES all members with package or internal 431 | # scope will be included in the documentation. 432 | # The default value is: NO. 433 | 434 | EXTRACT_PACKAGE = NO 435 | 436 | # If the EXTRACT_STATIC tag is set to YES all static members of a file will be 437 | # included in the documentation. 438 | # The default value is: NO. 439 | 440 | EXTRACT_STATIC = NO 441 | 442 | # If the EXTRACT_LOCAL_CLASSES tag is set to YES classes (and structs) defined 443 | # locally in source files will be included in the documentation. If set to NO 444 | # only classes defined in header files are included. Does not have any effect 445 | # for Java sources. 446 | # The default value is: YES. 447 | 448 | EXTRACT_LOCAL_CLASSES = YES 449 | 450 | # This flag is only useful for Objective-C code. When set to YES local methods, 451 | # which are defined in the implementation section but not in the interface are 452 | # included in the documentation. If set to NO only methods in the interface are 453 | # included. 454 | # The default value is: NO. 455 | 456 | EXTRACT_LOCAL_METHODS = NO 457 | 458 | # If this flag is set to YES, the members of anonymous namespaces will be 459 | # extracted and appear in the documentation as a namespace called 460 | # 'anonymous_namespace{file}', where file will be replaced with the base name of 461 | # the file that contains the anonymous namespace. By default anonymous namespace 462 | # are hidden. 463 | # The default value is: NO. 464 | 465 | EXTRACT_ANON_NSPACES = NO 466 | 467 | # If the HIDE_UNDOC_MEMBERS tag is set to YES, doxygen will hide all 468 | # undocumented members inside documented classes or files. If set to NO these 469 | # members will be included in the various overviews, but no documentation 470 | # section is generated. This option has no effect if EXTRACT_ALL is enabled. 471 | # The default value is: NO. 472 | 473 | HIDE_UNDOC_MEMBERS = NO 474 | 475 | # If the HIDE_UNDOC_CLASSES tag is set to YES, doxygen will hide all 476 | # undocumented classes that are normally visible in the class hierarchy. If set 477 | # to NO these classes will be included in the various overviews. This option has 478 | # no effect if EXTRACT_ALL is enabled. 479 | # The default value is: NO. 480 | 481 | HIDE_UNDOC_CLASSES = NO 482 | 483 | # If the HIDE_FRIEND_COMPOUNDS tag is set to YES, doxygen will hide all friend 484 | # (class|struct|union) declarations. If set to NO these declarations will be 485 | # included in the documentation. 486 | # The default value is: NO. 487 | 488 | HIDE_FRIEND_COMPOUNDS = NO 489 | 490 | # If the HIDE_IN_BODY_DOCS tag is set to YES, doxygen will hide any 491 | # documentation blocks found inside the body of a function. If set to NO these 492 | # blocks will be appended to the function's detailed documentation block. 493 | # The default value is: NO. 494 | 495 | HIDE_IN_BODY_DOCS = NO 496 | 497 | # The INTERNAL_DOCS tag determines if documentation that is typed after a 498 | # \internal command is included. If the tag is set to NO then the documentation 499 | # will be excluded. Set it to YES to include the internal documentation. 500 | # The default value is: NO. 501 | 502 | INTERNAL_DOCS = NO 503 | 504 | # If the CASE_SENSE_NAMES tag is set to NO then doxygen will only generate file 505 | # names in lower-case letters. If set to YES upper-case letters are also 506 | # allowed. This is useful if you have classes or files whose names only differ 507 | # in case and if your file system supports case sensitive file names. Windows 508 | # and Mac users are advised to set this option to NO. 509 | # The default value is: system dependent. 510 | 511 | CASE_SENSE_NAMES = NO 512 | 513 | # If the HIDE_SCOPE_NAMES tag is set to NO then doxygen will show members with 514 | # their full class and namespace scopes in the documentation. If set to YES the 515 | # scope will be hidden. 516 | # The default value is: NO. 517 | 518 | HIDE_SCOPE_NAMES = NO 519 | 520 | # If the SHOW_INCLUDE_FILES tag is set to YES then doxygen will put a list of 521 | # the files that are included by a file in the documentation of that file. 522 | # The default value is: YES. 523 | 524 | SHOW_INCLUDE_FILES = YES 525 | 526 | # If the SHOW_GROUPED_MEMB_INC tag is set to YES then Doxygen will add for each 527 | # grouped member an include statement to the documentation, telling the reader 528 | # which file to include in order to use the member. 529 | # The default value is: NO. 530 | 531 | SHOW_GROUPED_MEMB_INC = NO 532 | 533 | # If the FORCE_LOCAL_INCLUDES tag is set to YES then doxygen will list include 534 | # files with double quotes in the documentation rather than with sharp brackets. 535 | # The default value is: NO. 536 | 537 | FORCE_LOCAL_INCLUDES = NO 538 | 539 | # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the 540 | # documentation for inline members. 541 | # The default value is: YES. 542 | 543 | INLINE_INFO = YES 544 | 545 | # If the SORT_MEMBER_DOCS tag is set to YES then doxygen will sort the 546 | # (detailed) documentation of file and class members alphabetically by member 547 | # name. If set to NO the members will appear in declaration order. 548 | # The default value is: YES. 549 | 550 | SORT_MEMBER_DOCS = YES 551 | 552 | # If the SORT_BRIEF_DOCS tag is set to YES then doxygen will sort the brief 553 | # descriptions of file, namespace and class members alphabetically by member 554 | # name. If set to NO the members will appear in declaration order. Note that 555 | # this will also influence the order of the classes in the class list. 556 | # The default value is: NO. 557 | 558 | SORT_BRIEF_DOCS = NO 559 | 560 | # If the SORT_MEMBERS_CTORS_1ST tag is set to YES then doxygen will sort the 561 | # (brief and detailed) documentation of class members so that constructors and 562 | # destructors are listed first. If set to NO the constructors will appear in the 563 | # respective orders defined by SORT_BRIEF_DOCS and SORT_MEMBER_DOCS. 564 | # Note: If SORT_BRIEF_DOCS is set to NO this option is ignored for sorting brief 565 | # member documentation. 566 | # Note: If SORT_MEMBER_DOCS is set to NO this option is ignored for sorting 567 | # detailed member documentation. 568 | # The default value is: NO. 569 | 570 | SORT_MEMBERS_CTORS_1ST = NO 571 | 572 | # If the SORT_GROUP_NAMES tag is set to YES then doxygen will sort the hierarchy 573 | # of group names into alphabetical order. If set to NO the group names will 574 | # appear in their defined order. 575 | # The default value is: NO. 576 | 577 | SORT_GROUP_NAMES = NO 578 | 579 | # If the SORT_BY_SCOPE_NAME tag is set to YES, the class list will be sorted by 580 | # fully-qualified names, including namespaces. If set to NO, the class list will 581 | # be sorted only by class name, not including the namespace part. 582 | # Note: This option is not very useful if HIDE_SCOPE_NAMES is set to YES. 583 | # Note: This option applies only to the class list, not to the alphabetical 584 | # list. 585 | # The default value is: NO. 586 | 587 | SORT_BY_SCOPE_NAME = NO 588 | 589 | # If the STRICT_PROTO_MATCHING option is enabled and doxygen fails to do proper 590 | # type resolution of all parameters of a function it will reject a match between 591 | # the prototype and the implementation of a member function even if there is 592 | # only one candidate or it is obvious which candidate to choose by doing a 593 | # simple string match. By disabling STRICT_PROTO_MATCHING doxygen will still 594 | # accept a match between prototype and implementation in such cases. 595 | # The default value is: NO. 596 | 597 | STRICT_PROTO_MATCHING = NO 598 | 599 | # The GENERATE_TODOLIST tag can be used to enable ( YES) or disable ( NO) the 600 | # todo list. This list is created by putting \todo commands in the 601 | # documentation. 602 | # The default value is: YES. 603 | 604 | GENERATE_TODOLIST = YES 605 | 606 | # The GENERATE_TESTLIST tag can be used to enable ( YES) or disable ( NO) the 607 | # test list. This list is created by putting \test commands in the 608 | # documentation. 609 | # The default value is: YES. 610 | 611 | GENERATE_TESTLIST = YES 612 | 613 | # The GENERATE_BUGLIST tag can be used to enable ( YES) or disable ( NO) the bug 614 | # list. This list is created by putting \bug commands in the documentation. 615 | # The default value is: YES. 616 | 617 | GENERATE_BUGLIST = YES 618 | 619 | # The GENERATE_DEPRECATEDLIST tag can be used to enable ( YES) or disable ( NO) 620 | # the deprecated list. This list is created by putting \deprecated commands in 621 | # the documentation. 622 | # The default value is: YES. 623 | 624 | GENERATE_DEPRECATEDLIST= YES 625 | 626 | # The ENABLED_SECTIONS tag can be used to enable conditional documentation 627 | # sections, marked by \if ... \endif and \cond 628 | # ... \endcond blocks. 629 | 630 | ENABLED_SECTIONS = 631 | 632 | # The MAX_INITIALIZER_LINES tag determines the maximum number of lines that the 633 | # initial value of a variable or macro / define can have for it to appear in the 634 | # documentation. If the initializer consists of more lines than specified here 635 | # it will be hidden. Use a value of 0 to hide initializers completely. The 636 | # appearance of the value of individual variables and macros / defines can be 637 | # controlled using \showinitializer or \hideinitializer command in the 638 | # documentation regardless of this setting. 639 | # Minimum value: 0, maximum value: 10000, default value: 30. 640 | 641 | MAX_INITIALIZER_LINES = 30 642 | 643 | # Set the SHOW_USED_FILES tag to NO to disable the list of files generated at 644 | # the bottom of the documentation of classes and structs. If set to YES the list 645 | # will mention the files that were used to generate the documentation. 646 | # The default value is: YES. 647 | 648 | SHOW_USED_FILES = NO 649 | 650 | # Set the SHOW_FILES tag to NO to disable the generation of the Files page. This 651 | # will remove the Files entry from the Quick Index and from the Folder Tree View 652 | # (if specified). 653 | # The default value is: YES. 654 | 655 | SHOW_FILES = NO 656 | 657 | # Set the SHOW_NAMESPACES tag to NO to disable the generation of the Namespaces 658 | # page. This will remove the Namespaces entry from the Quick Index and from the 659 | # Folder Tree View (if specified). 660 | # The default value is: YES. 661 | 662 | SHOW_NAMESPACES = NO 663 | 664 | # The FILE_VERSION_FILTER tag can be used to specify a program or script that 665 | # doxygen should invoke to get the current version for each file (typically from 666 | # the version control system). Doxygen will invoke the program by executing (via 667 | # popen()) the command command input-file, where command is the value of the 668 | # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided 669 | # by doxygen. Whatever the program writes to standard output is used as the file 670 | # version. For an example see the documentation. 671 | 672 | FILE_VERSION_FILTER = 673 | 674 | # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed 675 | # by doxygen. The layout file controls the global structure of the generated 676 | # output files in an output format independent way. To create the layout file 677 | # that represents doxygen's defaults, run doxygen with the -l option. You can 678 | # optionally specify a file name after the option, if omitted DoxygenLayout.xml 679 | # will be used as the name of the layout file. 680 | # 681 | # Note that if you run doxygen from a directory containing a file called 682 | # DoxygenLayout.xml, doxygen will parse it automatically even if the LAYOUT_FILE 683 | # tag is left empty. 684 | 685 | LAYOUT_FILE = manual.xml 686 | 687 | # The CITE_BIB_FILES tag can be used to specify one or more bib files containing 688 | # the reference definitions. This must be a list of .bib files. The .bib 689 | # extension is automatically appended if omitted. This requires the bibtex tool 690 | # to be installed. See also http://en.wikipedia.org/wiki/BibTeX for more info. 691 | # For LaTeX the style of the bibliography can be controlled using 692 | # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the 693 | # search path. See also \cite for info how to create references. 694 | 695 | CITE_BIB_FILES = 696 | 697 | #--------------------------------------------------------------------------- 698 | # Configuration options related to warning and progress messages 699 | #--------------------------------------------------------------------------- 700 | 701 | # The QUIET tag can be used to turn on/off the messages that are generated to 702 | # standard output by doxygen. If QUIET is set to YES this implies that the 703 | # messages are off. 704 | # The default value is: NO. 705 | 706 | QUIET = NO 707 | 708 | # The WARNINGS tag can be used to turn on/off the warning messages that are 709 | # generated to standard error ( stderr) by doxygen. If WARNINGS is set to YES 710 | # this implies that the warnings are on. 711 | # 712 | # Tip: Turn warnings on while writing the documentation. 713 | # The default value is: YES. 714 | 715 | WARNINGS = YES 716 | 717 | # If the WARN_IF_UNDOCUMENTED tag is set to YES, then doxygen will generate 718 | # warnings for undocumented members. If EXTRACT_ALL is set to YES then this flag 719 | # will automatically be disabled. 720 | # The default value is: YES. 721 | 722 | WARN_IF_UNDOCUMENTED = YES 723 | 724 | # If the WARN_IF_DOC_ERROR tag is set to YES, doxygen will generate warnings for 725 | # potential errors in the documentation, such as not documenting some parameters 726 | # in a documented function, or documenting parameters that don't exist or using 727 | # markup commands wrongly. 728 | # The default value is: YES. 729 | 730 | WARN_IF_DOC_ERROR = YES 731 | 732 | # This WARN_NO_PARAMDOC option can be enabled to get warnings for functions that 733 | # are documented, but have no documentation for their parameters or return 734 | # value. If set to NO doxygen will only warn about wrong or incomplete parameter 735 | # documentation, but not about the absence of documentation. 736 | # The default value is: NO. 737 | 738 | WARN_NO_PARAMDOC = NO 739 | 740 | # The WARN_FORMAT tag determines the format of the warning messages that doxygen 741 | # can produce. The string should contain the $file, $line, and $text tags, which 742 | # will be replaced by the file and line number from which the warning originated 743 | # and the warning text. Optionally the format may contain $version, which will 744 | # be replaced by the version of the file (if it could be obtained via 745 | # FILE_VERSION_FILTER) 746 | # The default value is: $file:$line: $text. 747 | 748 | WARN_FORMAT = "$file:$line: $text" 749 | 750 | # The WARN_LOGFILE tag can be used to specify a file to which warning and error 751 | # messages should be written. If left blank the output is written to standard 752 | # error (stderr). 753 | 754 | WARN_LOGFILE = 755 | 756 | #--------------------------------------------------------------------------- 757 | # Configuration options related to the input files 758 | #--------------------------------------------------------------------------- 759 | 760 | # The INPUT tag is used to specify the files and/or directories that contain 761 | # documented source files. You may enter file names like myfile.cpp or 762 | # directories like /usr/src/myproject. Separate the files or directories with 763 | # spaces. 764 | # Note: If this tag is empty the current directory is searched. 765 | 766 | INPUT = ../src 767 | 768 | # This tag can be used to specify the character encoding of the source files 769 | # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses 770 | # libiconv (or the iconv built into libc) for the transcoding. See the libiconv 771 | # documentation (see: http://www.gnu.org/software/libiconv) for the list of 772 | # possible encodings. 773 | # The default value is: UTF-8. 774 | 775 | INPUT_ENCODING = UTF-8 776 | 777 | # If the value of the INPUT tag contains directories, you can use the 778 | # FILE_PATTERNS tag to specify one or more wildcard patterns (like *.cpp and 779 | # *.h) to filter out the source-files in the directories. If left blank the 780 | # following patterns are tested:*.c, *.cc, *.cxx, *.cpp, *.c++, *.java, *.ii, 781 | # *.ixx, *.ipp, *.i++, *.inl, *.idl, *.ddl, *.odl, *.h, *.hh, *.hxx, *.hpp, 782 | # *.h++, *.cs, *.d, *.php, *.php4, *.php5, *.phtml, *.inc, *.m, *.markdown, 783 | # *.md, *.mm, *.dox, *.py, *.f90, *.f, *.for, *.tcl, *.vhd, *.vhdl, *.ucf, 784 | # *.qsf, *.as and *.js. 785 | 786 | FILE_PATTERNS = *.c \ 787 | *.cc \ 788 | *.cxx \ 789 | *.cpp \ 790 | *.c++ \ 791 | *.h \ 792 | *.hh \ 793 | *.hxx \ 794 | *.hpp \ 795 | *.h++ \ 796 | *.inc \ 797 | *.markdown \ 798 | *.md 799 | 800 | # The RECURSIVE tag can be used to specify whether or not subdirectories should 801 | # be searched for input files as well. 802 | # The default value is: NO. 803 | 804 | RECURSIVE = YES 805 | 806 | # The EXCLUDE tag can be used to specify files and/or directories that should be 807 | # excluded from the INPUT source files. This way you can easily exclude a 808 | # subdirectory from a directory tree whose root is specified with the INPUT tag. 809 | # 810 | # Note that relative paths are relative to the directory from which doxygen is 811 | # run. 812 | 813 | EXCLUDE = 814 | 815 | # The EXCLUDE_SYMLINKS tag can be used to select whether or not files or 816 | # directories that are symbolic links (a Unix file system feature) are excluded 817 | # from the input. 818 | # The default value is: NO. 819 | 820 | EXCLUDE_SYMLINKS = NO 821 | 822 | # If the value of the INPUT tag contains directories, you can use the 823 | # EXCLUDE_PATTERNS tag to specify one or more wildcard patterns to exclude 824 | # certain files from those directories. 825 | # 826 | # Note that the wildcards are matched against the file with absolute path, so to 827 | # exclude all test directories for example use the pattern */test/* 828 | 829 | EXCLUDE_PATTERNS = 830 | 831 | # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 832 | # (namespaces, classes, functions, etc.) that should be excluded from the 833 | # output. The symbol name can be a fully qualified name, a word, or if the 834 | # wildcard * is used, a substring. Examples: ANamespace, AClass, 835 | # AClass::ANamespace, ANamespace::*Test 836 | # 837 | # Note that the wildcards are matched against the file with absolute path, so to 838 | # exclude all test directories use the pattern */test/* 839 | 840 | EXCLUDE_SYMBOLS = 841 | 842 | # The EXAMPLE_PATH tag can be used to specify one or more files or directories 843 | # that contain example code fragments that are included (see the \include 844 | # command). 845 | 846 | EXAMPLE_PATH = 847 | 848 | # If the value of the EXAMPLE_PATH tag contains directories, you can use the 849 | # EXAMPLE_PATTERNS tag to specify one or more wildcard pattern (like *.cpp and 850 | # *.h) to filter out the source-files in the directories. If left blank all 851 | # files are included. 852 | 853 | EXAMPLE_PATTERNS = * 854 | 855 | # If the EXAMPLE_RECURSIVE tag is set to YES then subdirectories will be 856 | # searched for input files to be used with the \include or \dontinclude commands 857 | # irrespective of the value of the RECURSIVE tag. 858 | # The default value is: NO. 859 | 860 | EXAMPLE_RECURSIVE = NO 861 | 862 | # The IMAGE_PATH tag can be used to specify one or more files or directories 863 | # that contain images that are to be included in the documentation (see the 864 | # \image command). 865 | 866 | IMAGE_PATH = ../res 867 | 868 | # The INPUT_FILTER tag can be used to specify a program that doxygen should 869 | # invoke to filter for each input file. Doxygen will invoke the filter program 870 | # by executing (via popen()) the command: 871 | # 872 | # 873 | # 874 | # where is the value of the INPUT_FILTER tag, and is the 875 | # name of an input file. Doxygen will then use the output that the filter 876 | # program writes to standard output. If FILTER_PATTERNS is specified, this tag 877 | # will be ignored. 878 | # 879 | # Note that the filter must not add or remove lines; it is applied before the 880 | # code is scanned, but not when the output code is generated. If lines are added 881 | # or removed, the anchors will not be placed correctly. 882 | 883 | INPUT_FILTER = 884 | 885 | # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern 886 | # basis. Doxygen will compare the file name with each pattern and apply the 887 | # filter if there is a match. The filters are a list of the form: pattern=filter 888 | # (like *.cpp=my_cpp_filter). See INPUT_FILTER for further information on how 889 | # filters are used. If the FILTER_PATTERNS tag is empty or if none of the 890 | # patterns match the file name, INPUT_FILTER is applied. 891 | 892 | FILTER_PATTERNS = 893 | 894 | # If the FILTER_SOURCE_FILES tag is set to YES, the input filter (if set using 895 | # INPUT_FILTER ) will also be used to filter the input files that are used for 896 | # producing the source files to browse (i.e. when SOURCE_BROWSER is set to YES). 897 | # The default value is: NO. 898 | 899 | FILTER_SOURCE_FILES = NO 900 | 901 | # The FILTER_SOURCE_PATTERNS tag can be used to specify source filters per file 902 | # pattern. A pattern will override the setting for FILTER_PATTERN (if any) and 903 | # it is also possible to disable source filtering for a specific pattern using 904 | # *.ext= (so without naming a filter). 905 | # This tag requires that the tag FILTER_SOURCE_FILES is set to YES. 906 | 907 | FILTER_SOURCE_PATTERNS = 908 | 909 | # If the USE_MDFILE_AS_MAINPAGE tag refers to the name of a markdown file that 910 | # is part of the input, its contents will be placed on the main page 911 | # (index.html). This can be useful if you have a project on for instance GitHub 912 | # and want to reuse the introduction page also for the doxygen output. 913 | 914 | USE_MDFILE_AS_MAINPAGE = 915 | 916 | #--------------------------------------------------------------------------- 917 | # Configuration options related to source browsing 918 | #--------------------------------------------------------------------------- 919 | 920 | # If the SOURCE_BROWSER tag is set to YES then a list of source files will be 921 | # generated. Documented entities will be cross-referenced with these sources. 922 | # 923 | # Note: To get rid of all source code in the generated output, make sure that 924 | # also VERBATIM_HEADERS is set to NO. 925 | # The default value is: NO. 926 | 927 | SOURCE_BROWSER = NO 928 | 929 | # Setting the INLINE_SOURCES tag to YES will include the body of functions, 930 | # classes and enums directly into the documentation. 931 | # The default value is: NO. 932 | 933 | INLINE_SOURCES = NO 934 | 935 | # Setting the STRIP_CODE_COMMENTS tag to YES will instruct doxygen to hide any 936 | # special comment blocks from generated source code fragments. Normal C, C++ and 937 | # Fortran comments will always remain visible. 938 | # The default value is: YES. 939 | 940 | STRIP_CODE_COMMENTS = YES 941 | 942 | # If the REFERENCED_BY_RELATION tag is set to YES then for each documented 943 | # function all documented functions referencing it will be listed. 944 | # The default value is: NO. 945 | 946 | REFERENCED_BY_RELATION = NO 947 | 948 | # If the REFERENCES_RELATION tag is set to YES then for each documented function 949 | # all documented entities called/used by that function will be listed. 950 | # The default value is: NO. 951 | 952 | REFERENCES_RELATION = NO 953 | 954 | # If the REFERENCES_LINK_SOURCE tag is set to YES and SOURCE_BROWSER tag is set 955 | # to YES, then the hyperlinks from functions in REFERENCES_RELATION and 956 | # REFERENCED_BY_RELATION lists will link to the source code. Otherwise they will 957 | # link to the documentation. 958 | # The default value is: YES. 959 | 960 | REFERENCES_LINK_SOURCE = YES 961 | 962 | # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the 963 | # source code will show a tooltip with additional information such as prototype, 964 | # brief description and links to the definition and documentation. Since this 965 | # will make the HTML file larger and loading of large files a bit slower, you 966 | # can opt to disable this feature. 967 | # The default value is: YES. 968 | # This tag requires that the tag SOURCE_BROWSER is set to YES. 969 | 970 | SOURCE_TOOLTIPS = YES 971 | 972 | # If the USE_HTAGS tag is set to YES then the references to source code will 973 | # point to the HTML generated by the htags(1) tool instead of doxygen built-in 974 | # source browser. The htags tool is part of GNU's global source tagging system 975 | # (see http://www.gnu.org/software/global/global.html). You will need version 976 | # 4.8.6 or higher. 977 | # 978 | # To use it do the following: 979 | # - Install the latest version of global 980 | # - Enable SOURCE_BROWSER and USE_HTAGS in the config file 981 | # - Make sure the INPUT points to the root of the source tree 982 | # - Run doxygen as normal 983 | # 984 | # Doxygen will invoke htags (and that will in turn invoke gtags), so these 985 | # tools must be available from the command line (i.e. in the search path). 986 | # 987 | # The result: instead of the source browser generated by doxygen, the links to 988 | # source code will now point to the output of htags. 989 | # The default value is: NO. 990 | # This tag requires that the tag SOURCE_BROWSER is set to YES. 991 | 992 | USE_HTAGS = NO 993 | 994 | # If the VERBATIM_HEADERS tag is set the YES then doxygen will generate a 995 | # verbatim copy of the header file for each class for which an include is 996 | # specified. Set to NO to disable this. 997 | # See also: Section \class. 998 | # The default value is: YES. 999 | 1000 | VERBATIM_HEADERS = YES 1001 | 1002 | # If the CLANG_ASSISTED_PARSING tag is set to YES, then doxygen will use the 1003 | # clang parser (see: http://clang.llvm.org/) for more accurate parsing at the 1004 | # cost of reduced performance. This can be particularly helpful with template 1005 | # rich C++ code for which doxygen's built-in parser lacks the necessary type 1006 | # information. 1007 | # Note: The availability of this option depends on whether or not doxygen was 1008 | # compiled with the --with-libclang option. 1009 | # The default value is: NO. 1010 | 1011 | # CLANG_ASSISTED_PARSING = NO 1012 | 1013 | # If clang assisted parsing is enabled you can provide the compiler with command 1014 | # line options that you would normally use when invoking the compiler. Note that 1015 | # the include paths will already be set by doxygen for the files and directories 1016 | # specified with INPUT and INCLUDE_PATH. 1017 | # This tag requires that the tag CLANG_ASSISTED_PARSING is set to YES. 1018 | 1019 | # CLANG_OPTIONS = 1020 | 1021 | #--------------------------------------------------------------------------- 1022 | # Configuration options related to the alphabetical class index 1023 | #--------------------------------------------------------------------------- 1024 | 1025 | # If the ALPHABETICAL_INDEX tag is set to YES, an alphabetical index of all 1026 | # compounds will be generated. Enable this if the project contains a lot of 1027 | # classes, structs, unions or interfaces. 1028 | # The default value is: YES. 1029 | 1030 | ALPHABETICAL_INDEX = YES 1031 | 1032 | # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in 1033 | # which the alphabetical index list will be split. 1034 | # Minimum value: 1, maximum value: 20, default value: 5. 1035 | # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. 1036 | 1037 | COLS_IN_ALPHA_INDEX = 5 1038 | 1039 | # In case all classes in a project start with a common prefix, all classes will 1040 | # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag 1041 | # can be used to specify a prefix (or a list of prefixes) that should be ignored 1042 | # while generating the index headers. 1043 | # This tag requires that the tag ALPHABETICAL_INDEX is set to YES. 1044 | 1045 | IGNORE_PREFIX = 1046 | 1047 | #--------------------------------------------------------------------------- 1048 | # Configuration options related to the HTML output 1049 | #--------------------------------------------------------------------------- 1050 | 1051 | # If the GENERATE_HTML tag is set to YES doxygen will generate HTML output 1052 | # The default value is: YES. 1053 | 1054 | GENERATE_HTML = YES 1055 | 1056 | # The HTML_OUTPUT tag is used to specify where the HTML docs will be put. If a 1057 | # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of 1058 | # it. 1059 | # The default directory is: html. 1060 | # This tag requires that the tag GENERATE_HTML is set to YES. 1061 | 1062 | HTML_OUTPUT = manual.chs 1063 | 1064 | # The HTML_FILE_EXTENSION tag can be used to specify the file extension for each 1065 | # generated HTML page (for example: .htm, .php, .asp). 1066 | # The default value is: .html. 1067 | # This tag requires that the tag GENERATE_HTML is set to YES. 1068 | 1069 | HTML_FILE_EXTENSION = .html 1070 | 1071 | # The HTML_HEADER tag can be used to specify a user-defined HTML header file for 1072 | # each generated HTML page. If the tag is left blank doxygen will generate a 1073 | # standard header. 1074 | # 1075 | # To get valid HTML the header file that includes any scripts and style sheets 1076 | # that doxygen needs, which is dependent on the configuration options used (e.g. 1077 | # the setting GENERATE_TREEVIEW). It is highly recommended to start with a 1078 | # default header using 1079 | # doxygen -w html new_header.html new_footer.html new_stylesheet.css 1080 | # YourConfigFile 1081 | # and then modify the file new_header.html. See also section "Doxygen usage" 1082 | # for information on how to generate the default header that doxygen normally 1083 | # uses. 1084 | # Note: The header is subject to change so you typically have to regenerate the 1085 | # default header when upgrading to a newer version of doxygen. For a description 1086 | # of the possible markers and block names see the documentation. 1087 | # This tag requires that the tag GENERATE_HTML is set to YES. 1088 | 1089 | HTML_HEADER = manual.html 1090 | 1091 | # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each 1092 | # generated HTML page. If the tag is left blank doxygen will generate a standard 1093 | # footer. See HTML_HEADER for more information on how to generate a default 1094 | # footer and what special commands can be used inside the footer. See also 1095 | # section "Doxygen usage" for information on how to generate the default footer 1096 | # that doxygen normally uses. 1097 | # This tag requires that the tag GENERATE_HTML is set to YES. 1098 | 1099 | HTML_FOOTER = 1100 | 1101 | # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style 1102 | # sheet that is used by each HTML page. It can be used to fine-tune the look of 1103 | # the HTML output. If left blank doxygen will generate a default style sheet. 1104 | # See also section "Doxygen usage" for information on how to generate the style 1105 | # sheet that doxygen normally uses. 1106 | # Note: It is recommended to use HTML_EXTRA_STYLESHEET instead of this tag, as 1107 | # it is more robust and this tag (HTML_STYLESHEET) will in the future become 1108 | # obsolete. 1109 | # This tag requires that the tag GENERATE_HTML is set to YES. 1110 | 1111 | HTML_STYLESHEET = 1112 | 1113 | # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined 1114 | # cascading style sheets that are included after the standard style sheets 1115 | # created by doxygen. Using this option one can overrule certain style aspects. 1116 | # This is preferred over using HTML_STYLESHEET since it does not replace the 1117 | # standard style sheet and is therefor more robust against future updates. 1118 | # Doxygen will copy the style sheet files to the output directory. 1119 | # Note: The order of the extra stylesheet files is of importance (e.g. the last 1120 | # stylesheet in the list overrules the setting of the previous ones in the 1121 | # list). For an example see the documentation. 1122 | # This tag requires that the tag GENERATE_HTML is set to YES. 1123 | 1124 | HTML_EXTRA_STYLESHEET = manual.css 1125 | 1126 | # The HTML_EXTRA_FILES tag can be used to specify one or more extra images or 1127 | # other source files which should be copied to the HTML output directory. Note 1128 | # that these files will be copied to the base HTML output directory. Use the 1129 | # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these 1130 | # files. In the HTML_STYLESHEET file, use the file name only. Also note that the 1131 | # files will be copied as-is; there are no commands or markers available. 1132 | # This tag requires that the tag GENERATE_HTML is set to YES. 1133 | 1134 | HTML_EXTRA_FILES = 1135 | 1136 | # The HTML_COLORSTYLE_HUE tag controls the color of the HTML output. Doxygen 1137 | # will adjust the colors in the stylesheet and background images according to 1138 | # this color. Hue is specified as an angle on a colorwheel, see 1139 | # http://en.wikipedia.org/wiki/Hue for more information. For instance the value 1140 | # 0 represents red, 60 is yellow, 120 is green, 180 is cyan, 240 is blue, 300 1141 | # purple, and 360 is red again. 1142 | # Minimum value: 0, maximum value: 359, default value: 220. 1143 | # This tag requires that the tag GENERATE_HTML is set to YES. 1144 | 1145 | HTML_COLORSTYLE_HUE = 220 1146 | 1147 | # The HTML_COLORSTYLE_SAT tag controls the purity (or saturation) of the colors 1148 | # in the HTML output. For a value of 0 the output will use grayscales only. A 1149 | # value of 255 will produce the most vivid colors. 1150 | # Minimum value: 0, maximum value: 255, default value: 100. 1151 | # This tag requires that the tag GENERATE_HTML is set to YES. 1152 | 1153 | HTML_COLORSTYLE_SAT = 100 1154 | 1155 | # The HTML_COLORSTYLE_GAMMA tag controls the gamma correction applied to the 1156 | # luminance component of the colors in the HTML output. Values below 100 1157 | # gradually make the output lighter, whereas values above 100 make the output 1158 | # darker. The value divided by 100 is the actual gamma applied, so 80 represents 1159 | # a gamma of 0.8, The value 220 represents a gamma of 2.2, and 100 does not 1160 | # change the gamma. 1161 | # Minimum value: 40, maximum value: 240, default value: 80. 1162 | # This tag requires that the tag GENERATE_HTML is set to YES. 1163 | 1164 | HTML_COLORSTYLE_GAMMA = 80 1165 | 1166 | # If the HTML_TIMESTAMP tag is set to YES then the footer of each generated HTML 1167 | # page will contain the date and time when the page was generated. Setting this 1168 | # to NO can help when comparing the output of multiple runs. 1169 | # The default value is: YES. 1170 | # This tag requires that the tag GENERATE_HTML is set to YES. 1171 | 1172 | HTML_TIMESTAMP = YES 1173 | 1174 | # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 1175 | # documentation will contain sections that can be hidden and shown after the 1176 | # page has loaded. 1177 | # The default value is: NO. 1178 | # This tag requires that the tag GENERATE_HTML is set to YES. 1179 | 1180 | HTML_DYNAMIC_SECTIONS = NO 1181 | 1182 | # With HTML_INDEX_NUM_ENTRIES one can control the preferred number of entries 1183 | # shown in the various tree structured indices initially; the user can expand 1184 | # and collapse entries dynamically later on. Doxygen will expand the tree to 1185 | # such a level that at most the specified number of entries are visible (unless 1186 | # a fully collapsed tree already exceeds this amount). So setting the number of 1187 | # entries 1 will produce a full collapsed tree by default. 0 is a special value 1188 | # representing an infinite number of entries and will result in a full expanded 1189 | # tree by default. 1190 | # Minimum value: 0, maximum value: 9999, default value: 100. 1191 | # This tag requires that the tag GENERATE_HTML is set to YES. 1192 | 1193 | HTML_INDEX_NUM_ENTRIES = 100 1194 | 1195 | # If the GENERATE_DOCSET tag is set to YES, additional index files will be 1196 | # generated that can be used as input for Apple's Xcode 3 integrated development 1197 | # environment (see: http://developer.apple.com/tools/xcode/), introduced with 1198 | # OSX 10.5 (Leopard). To create a documentation set, doxygen will generate a 1199 | # Makefile in the HTML output directory. Running make will produce the docset in 1200 | # that directory and running make install will install the docset in 1201 | # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at 1202 | # startup. See http://developer.apple.com/tools/creatingdocsetswithdoxygen.html 1203 | # for more information. 1204 | # The default value is: NO. 1205 | # This tag requires that the tag GENERATE_HTML is set to YES. 1206 | 1207 | GENERATE_DOCSET = NO 1208 | 1209 | # This tag determines the name of the docset feed. A documentation feed provides 1210 | # an umbrella under which multiple documentation sets from a single provider 1211 | # (such as a company or product suite) can be grouped. 1212 | # The default value is: Doxygen generated docs. 1213 | # This tag requires that the tag GENERATE_DOCSET is set to YES. 1214 | 1215 | DOCSET_FEEDNAME = "Doxygen generated docs" 1216 | 1217 | # This tag specifies a string that should uniquely identify the documentation 1218 | # set bundle. This should be a reverse domain-name style string, e.g. 1219 | # com.mycompany.MyDocSet. Doxygen will append .docset to the name. 1220 | # The default value is: org.doxygen.Project. 1221 | # This tag requires that the tag GENERATE_DOCSET is set to YES. 1222 | 1223 | DOCSET_BUNDLE_ID = org.doxygen.Project 1224 | 1225 | # The DOCSET_PUBLISHER_ID tag specifies a string that should uniquely identify 1226 | # the documentation publisher. This should be a reverse domain-name style 1227 | # string, e.g. com.mycompany.MyDocSet.documentation. 1228 | # The default value is: org.doxygen.Publisher. 1229 | # This tag requires that the tag GENERATE_DOCSET is set to YES. 1230 | 1231 | DOCSET_PUBLISHER_ID = org.doxygen.Publisher 1232 | 1233 | # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher. 1234 | # The default value is: Publisher. 1235 | # This tag requires that the tag GENERATE_DOCSET is set to YES. 1236 | 1237 | DOCSET_PUBLISHER_NAME = Publisher 1238 | 1239 | # If the GENERATE_HTMLHELP tag is set to YES then doxygen generates three 1240 | # additional HTML index files: index.hhp, index.hhc, and index.hhk. The 1241 | # index.hhp is a project file that can be read by Microsoft's HTML Help Workshop 1242 | # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on 1243 | # Windows. 1244 | # 1245 | # The HTML Help Workshop contains a compiler that can convert all HTML output 1246 | # generated by doxygen into a single compiled HTML file (.chm). Compiled HTML 1247 | # files are now used as the Windows 98 help format, and will replace the old 1248 | # Windows help format (.hlp) on all Windows platforms in the future. Compressed 1249 | # HTML files also contain an index, a table of contents, and you can search for 1250 | # words in the documentation. The HTML workshop also contains a viewer for 1251 | # compressed HTML files. 1252 | # The default value is: NO. 1253 | # This tag requires that the tag GENERATE_HTML is set to YES. 1254 | 1255 | GENERATE_HTMLHELP = NO 1256 | 1257 | # The CHM_FILE tag can be used to specify the file name of the resulting .chm 1258 | # file. You can add a path in front of the file if the result should not be 1259 | # written to the html output directory. 1260 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1261 | 1262 | CHM_FILE = ../NERvLibrary.chm 1263 | 1264 | # The HHC_LOCATION tag can be used to specify the location (absolute path 1265 | # including file name) of the HTML help compiler ( hhc.exe). If non-empty 1266 | # doxygen will try to run the HTML help compiler on the generated index.hhp. 1267 | # The file has to be specified with full path. 1268 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1269 | 1270 | HHC_LOCATION = "D:/Office/HTML Help Workshop/hhc.exe" 1271 | 1272 | # The GENERATE_CHI flag controls if a separate .chi index file is generated ( 1273 | # YES) or that it should be included in the master .chm file ( NO). 1274 | # The default value is: NO. 1275 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1276 | 1277 | GENERATE_CHI = NO 1278 | 1279 | # The CHM_INDEX_ENCODING is used to encode HtmlHelp index ( hhk), content ( hhc) 1280 | # and project file content. 1281 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1282 | 1283 | CHM_INDEX_ENCODING = 1284 | 1285 | # The BINARY_TOC flag controls whether a binary table of contents is generated ( 1286 | # YES) or a normal table of contents ( NO) in the .chm file. Furthermore it 1287 | # enables the Previous and Next buttons. 1288 | # The default value is: NO. 1289 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1290 | 1291 | BINARY_TOC = NO 1292 | 1293 | # The TOC_EXPAND flag can be set to YES to add extra items for group members to 1294 | # the table of contents of the HTML help documentation and to the tree view. 1295 | # The default value is: NO. 1296 | # This tag requires that the tag GENERATE_HTMLHELP is set to YES. 1297 | 1298 | TOC_EXPAND = NO 1299 | 1300 | # If the GENERATE_QHP tag is set to YES and both QHP_NAMESPACE and 1301 | # QHP_VIRTUAL_FOLDER are set, an additional index file will be generated that 1302 | # can be used as input for Qt's qhelpgenerator to generate a Qt Compressed Help 1303 | # (.qch) of the generated HTML documentation. 1304 | # The default value is: NO. 1305 | # This tag requires that the tag GENERATE_HTML is set to YES. 1306 | 1307 | GENERATE_QHP = NO 1308 | 1309 | # If the QHG_LOCATION tag is specified, the QCH_FILE tag can be used to specify 1310 | # the file name of the resulting .qch file. The path specified is relative to 1311 | # the HTML output folder. 1312 | # This tag requires that the tag GENERATE_QHP is set to YES. 1313 | 1314 | QCH_FILE = 1315 | 1316 | # The QHP_NAMESPACE tag specifies the namespace to use when generating Qt Help 1317 | # Project output. For more information please see Qt Help Project / Namespace 1318 | # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace). 1319 | # The default value is: org.doxygen.Project. 1320 | # This tag requires that the tag GENERATE_QHP is set to YES. 1321 | 1322 | QHP_NAMESPACE = org.doxygen.Project 1323 | 1324 | # The QHP_VIRTUAL_FOLDER tag specifies the namespace to use when generating Qt 1325 | # Help Project output. For more information please see Qt Help Project / Virtual 1326 | # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual- 1327 | # folders). 1328 | # The default value is: doc. 1329 | # This tag requires that the tag GENERATE_QHP is set to YES. 1330 | 1331 | QHP_VIRTUAL_FOLDER = doc 1332 | 1333 | # If the QHP_CUST_FILTER_NAME tag is set, it specifies the name of a custom 1334 | # filter to add. For more information please see Qt Help Project / Custom 1335 | # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- 1336 | # filters). 1337 | # This tag requires that the tag GENERATE_QHP is set to YES. 1338 | 1339 | QHP_CUST_FILTER_NAME = 1340 | 1341 | # The QHP_CUST_FILTER_ATTRS tag specifies the list of the attributes of the 1342 | # custom filter to add. For more information please see Qt Help Project / Custom 1343 | # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom- 1344 | # filters). 1345 | # This tag requires that the tag GENERATE_QHP is set to YES. 1346 | 1347 | QHP_CUST_FILTER_ATTRS = 1348 | 1349 | # The QHP_SECT_FILTER_ATTRS tag specifies the list of the attributes this 1350 | # project's filter section matches. Qt Help Project / Filter Attributes (see: 1351 | # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes). 1352 | # This tag requires that the tag GENERATE_QHP is set to YES. 1353 | 1354 | QHP_SECT_FILTER_ATTRS = 1355 | 1356 | # The QHG_LOCATION tag can be used to specify the location of Qt's 1357 | # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the 1358 | # generated .qhp file. 1359 | # This tag requires that the tag GENERATE_QHP is set to YES. 1360 | 1361 | QHG_LOCATION = 1362 | 1363 | # If the GENERATE_ECLIPSEHELP tag is set to YES, additional index files will be 1364 | # generated, together with the HTML files, they form an Eclipse help plugin. To 1365 | # install this plugin and make it available under the help contents menu in 1366 | # Eclipse, the contents of the directory containing the HTML and XML files needs 1367 | # to be copied into the plugins directory of eclipse. The name of the directory 1368 | # within the plugins directory should be the same as the ECLIPSE_DOC_ID value. 1369 | # After copying Eclipse needs to be restarted before the help appears. 1370 | # The default value is: NO. 1371 | # This tag requires that the tag GENERATE_HTML is set to YES. 1372 | 1373 | GENERATE_ECLIPSEHELP = NO 1374 | 1375 | # A unique identifier for the Eclipse help plugin. When installing the plugin 1376 | # the directory name containing the HTML and XML files should also have this 1377 | # name. Each documentation set should have its own identifier. 1378 | # The default value is: org.doxygen.Project. 1379 | # This tag requires that the tag GENERATE_ECLIPSEHELP is set to YES. 1380 | 1381 | ECLIPSE_DOC_ID = org.doxygen.Project 1382 | 1383 | # If you want full control over the layout of the generated HTML pages it might 1384 | # be necessary to disable the index and replace it with your own. The 1385 | # DISABLE_INDEX tag can be used to turn on/off the condensed index (tabs) at top 1386 | # of each HTML page. A value of NO enables the index and the value YES disables 1387 | # it. Since the tabs in the index contain the same information as the navigation 1388 | # tree, you can set this option to YES if you also set GENERATE_TREEVIEW to YES. 1389 | # The default value is: NO. 1390 | # This tag requires that the tag GENERATE_HTML is set to YES. 1391 | 1392 | DISABLE_INDEX = NO 1393 | 1394 | # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index 1395 | # structure should be generated to display hierarchical information. If the tag 1396 | # value is set to YES, a side panel will be generated containing a tree-like 1397 | # index structure (just like the one that is generated for HTML Help). For this 1398 | # to work a browser that supports JavaScript, DHTML, CSS and frames is required 1399 | # (i.e. any modern browser). Windows users are probably better off using the 1400 | # HTML help feature. Via custom stylesheets (see HTML_EXTRA_STYLESHEET) one can 1401 | # further fine-tune the look of the index. As an example, the default style 1402 | # sheet generated by doxygen has an example that shows how to put an image at 1403 | # the root of the tree instead of the PROJECT_NAME. Since the tree basically has 1404 | # the same information as the tab index, you could consider setting 1405 | # DISABLE_INDEX to YES when enabling this option. 1406 | # The default value is: NO. 1407 | # This tag requires that the tag GENERATE_HTML is set to YES. 1408 | 1409 | GENERATE_TREEVIEW = YES 1410 | 1411 | # The ENUM_VALUES_PER_LINE tag can be used to set the number of enum values that 1412 | # doxygen will group on one line in the generated HTML documentation. 1413 | # 1414 | # Note that a value of 0 will completely suppress the enum values from appearing 1415 | # in the overview section. 1416 | # Minimum value: 0, maximum value: 20, default value: 4. 1417 | # This tag requires that the tag GENERATE_HTML is set to YES. 1418 | 1419 | ENUM_VALUES_PER_LINE = 4 1420 | 1421 | # If the treeview is enabled (see GENERATE_TREEVIEW) then this tag can be used 1422 | # to set the initial width (in pixels) of the frame in which the tree is shown. 1423 | # Minimum value: 0, maximum value: 1500, default value: 250. 1424 | # This tag requires that the tag GENERATE_HTML is set to YES. 1425 | 1426 | TREEVIEW_WIDTH = 250 1427 | 1428 | # When the EXT_LINKS_IN_WINDOW option is set to YES doxygen will open links to 1429 | # external symbols imported via tag files in a separate window. 1430 | # The default value is: NO. 1431 | # This tag requires that the tag GENERATE_HTML is set to YES. 1432 | 1433 | EXT_LINKS_IN_WINDOW = NO 1434 | 1435 | # Use this tag to change the font size of LaTeX formulas included as images in 1436 | # the HTML documentation. When you change the font size after a successful 1437 | # doxygen run you need to manually remove any form_*.png images from the HTML 1438 | # output directory to force them to be regenerated. 1439 | # Minimum value: 8, maximum value: 50, default value: 10. 1440 | # This tag requires that the tag GENERATE_HTML is set to YES. 1441 | 1442 | FORMULA_FONTSIZE = 10 1443 | 1444 | # Use the FORMULA_TRANPARENT tag to determine whether or not the images 1445 | # generated for formulas are transparent PNGs. Transparent PNGs are not 1446 | # supported properly for IE 6.0, but are supported on all modern browsers. 1447 | # 1448 | # Note that when changing this option you need to delete any form_*.png files in 1449 | # the HTML output directory before the changes have effect. 1450 | # The default value is: YES. 1451 | # This tag requires that the tag GENERATE_HTML is set to YES. 1452 | 1453 | FORMULA_TRANSPARENT = YES 1454 | 1455 | # Enable the USE_MATHJAX option to render LaTeX formulas using MathJax (see 1456 | # http://www.mathjax.org) which uses client side Javascript for the rendering 1457 | # instead of using prerendered bitmaps. Use this if you do not have LaTeX 1458 | # installed or if you want to formulas look prettier in the HTML output. When 1459 | # enabled you may also need to install MathJax separately and configure the path 1460 | # to it using the MATHJAX_RELPATH option. 1461 | # The default value is: NO. 1462 | # This tag requires that the tag GENERATE_HTML is set to YES. 1463 | 1464 | USE_MATHJAX = NO 1465 | 1466 | # When MathJax is enabled you can set the default output format to be used for 1467 | # the MathJax output. See the MathJax site (see: 1468 | # http://docs.mathjax.org/en/latest/output.html) for more details. 1469 | # Possible values are: HTML-CSS (which is slower, but has the best 1470 | # compatibility), NativeMML (i.e. MathML) and SVG. 1471 | # The default value is: HTML-CSS. 1472 | # This tag requires that the tag USE_MATHJAX is set to YES. 1473 | 1474 | MATHJAX_FORMAT = HTML-CSS 1475 | 1476 | # When MathJax is enabled you need to specify the location relative to the HTML 1477 | # output directory using the MATHJAX_RELPATH option. The destination directory 1478 | # should contain the MathJax.js script. For instance, if the mathjax directory 1479 | # is located at the same level as the HTML output directory, then 1480 | # MATHJAX_RELPATH should be ../mathjax. The default value points to the MathJax 1481 | # Content Delivery Network so you can quickly see the result without installing 1482 | # MathJax. However, it is strongly recommended to install a local copy of 1483 | # MathJax from http://www.mathjax.org before deployment. 1484 | # The default value is: http://cdn.mathjax.org/mathjax/latest. 1485 | # This tag requires that the tag USE_MATHJAX is set to YES. 1486 | 1487 | MATHJAX_RELPATH = http://cdn.mathjax.org/mathjax/latest 1488 | 1489 | # The MATHJAX_EXTENSIONS tag can be used to specify one or more MathJax 1490 | # extension names that should be enabled during MathJax rendering. For example 1491 | # MATHJAX_EXTENSIONS = TeX/AMSmath TeX/AMSsymbols 1492 | # This tag requires that the tag USE_MATHJAX is set to YES. 1493 | 1494 | MATHJAX_EXTENSIONS = 1495 | 1496 | # The MATHJAX_CODEFILE tag can be used to specify a file with javascript pieces 1497 | # of code that will be used on startup of the MathJax code. See the MathJax site 1498 | # (see: http://docs.mathjax.org/en/latest/output.html) for more details. For an 1499 | # example see the documentation. 1500 | # This tag requires that the tag USE_MATHJAX is set to YES. 1501 | 1502 | MATHJAX_CODEFILE = 1503 | 1504 | # When the SEARCHENGINE tag is enabled doxygen will generate a search box for 1505 | # the HTML output. The underlying search engine uses javascript and DHTML and 1506 | # should work on any modern browser. Note that when using HTML help 1507 | # (GENERATE_HTMLHELP), Qt help (GENERATE_QHP), or docsets (GENERATE_DOCSET) 1508 | # there is already a search function so this one should typically be disabled. 1509 | # For large projects the javascript based search engine can be slow, then 1510 | # enabling SERVER_BASED_SEARCH may provide a better solution. It is possible to 1511 | # search using the keyboard; to jump to the search box use + S 1512 | # (what the is depends on the OS and browser, but it is typically 1513 | # , /