- Timestamp:
- Apr 30, 2008, 9:39:31 PM (17 years ago)
- Branches:
- feature/autosink, feature/cnn, feature/cnn_org, feature/constantq, feature/crepe, feature/crepe_org, feature/pitchshift, feature/pydocstrings, feature/timestretch, fix/ffmpeg5, master, pitchshift, sampler, timestretch, yinfft+
- Children:
- 98cc475
- Parents:
- 679441e
- Location:
- doc
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/devel.cfg
r679441e rfed9433 1 # Doxyfile 1. 4.61 # Doxyfile 1.5.3-20071008 2 2 3 3 # This file describes the settings to be used by the documentation system … … 15 15 #--------------------------------------------------------------------------- 16 16 17 # This tag specifies the encoding used for all characters in the config file that 18 # follow. The default is UTF-8 which is also the encoding used for all text before 19 # the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into 20 # libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of 21 # possible encodings. 22 23 DOXYFILE_ENCODING = UTF-8 24 17 25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded 18 26 # by quotes) that should identify the project. … … 24 32 # if some version control system is used. 25 33 26 #PROJECT_NUMBER = 0.3.0 34 PROJECT_NUMBER = 27 35 28 36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) … … 46 54 # information to generate all constant output in the proper language. 47 55 # The default language is English, other supported languages are: 48 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,49 # Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,50 # Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,51 # Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,52 # S wedish, and Ukrainian.56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 57 # Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, 58 # Italian, Japanese, Japanese-en (Japanese with English messages), Korean, 59 # Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian, 60 # Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. 53 61 54 62 OUTPUT_LANGUAGE = English 55 56 # This tag can be used to specify the encoding used in the generated output.57 # The encoding is not always determined by the language that is chosen,58 # but also whether or not the output is meant for Windows or non-Windows users.59 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES60 # forces the Windows encoding (this is the default for the Windows binary),61 # whereas setting the tag to NO uses a Unix-style encoding (the default for62 # all platforms other than Windows).63 64 USE_WINDOWS_ENCODING = NO65 63 66 64 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will … … 107 105 # to NO the shortest path that makes the file name unique will be used. 108 106 109 FULL_PATH_NAMES = NO107 FULL_PATH_NAMES = YES 110 108 111 109 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag … … 116 114 # path to strip. 117 115 118 STRIP_FROM_PATH = 116 STRIP_FROM_PATH = .. 119 117 120 118 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of … … 136 134 # will interpret the first line (until the first dot) of a JavaDoc-style 137 135 # comment as the brief description. If set to NO, the JavaDoc 138 # comments will behave just like the Qt-style comments (thus requiring an139 # explicit @brief command for a brief description.136 # comments will behave just like regular Qt-style comments 137 # (thus requiring an explicit @brief command for a brief description.) 140 138 141 139 JAVADOC_AUTOBRIEF = YES 140 141 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will 142 # interpret the first line (until the first dot) of a Qt-style 143 # comment as the brief description. If set to NO, the comments 144 # will behave just like regular Qt-style comments (thus requiring 145 # an explicit \brief command for a brief description.) 146 147 QT_AUTOBRIEF = NO 142 148 143 149 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen … … 205 211 BUILTIN_STL_SUPPORT = NO 206 212 213 # If you use Microsoft's C++/CLI language, you should set this option to YES to 214 # enable parsing support. 215 216 CPP_CLI_SUPPORT = NO 217 218 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 219 # Doxygen will parse them like normal C++ but will assume all classes use public 220 # instead of private inheritance when no explicit protection keyword is present. 221 222 SIP_SUPPORT = NO 223 207 224 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 208 225 # tag is set to YES, then doxygen will reuse the documentation of the first … … 253 270 254 271 EXTRACT_LOCAL_METHODS = NO 272 273 # If this flag is set to YES, the members of anonymous namespaces will be extracted 274 # and appear in the documentation as a namespace called 'anonymous_namespace{file}', 275 # where file will be replaced with the base name of the file that contains the anonymous 276 # namespace. By default anonymous namespace are hidden. 277 278 EXTRACT_ANON_NSPACES = NO 255 279 256 280 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all … … 388 412 # in the documentation. The default is NO. 389 413 390 SHOW_DIRECTORIES = NO414 SHOW_DIRECTORIES = YES 391 415 392 416 # The FILE_VERSION_FILTER tag can be used to specify a program or script that … … 443 467 # be obtained via FILE_VERSION_FILTER) 444 468 445 WARN_FORMAT = "$file:$line: $text "469 WARN_FORMAT = "$file:$line: $text " 446 470 447 471 # The WARN_LOGFILE tag can be used to specify a file to which warning … … 460 484 # with spaces. 461 485 462 INPUT = ../src \ 463 ../ext 486 INPUT = ../src ../ext 487 488 # This tag can be used to specify the character encoding of the source files that 489 # doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default 490 # input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. 491 # See http://www.gnu.org/software/libiconv for the list of possible encodings. 492 493 INPUT_ENCODING = UTF-8 464 494 465 495 # If the value of the INPUT tag contains directories, you can use the … … 476 506 # If left blank NO is used. 477 507 478 RECURSIVE = NO508 RECURSIVE = YES 479 509 480 510 # The EXCLUDE tag can be used to specify files and/or directories that should … … 498 528 EXCLUDE_PATTERNS = 499 529 530 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 531 # (namespaces, classes, functions, etc.) that should be excluded from the output. 532 # The symbol name can be a fully qualified name, a word, or if the wildcard * is used, 533 # a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test 534 535 EXCLUDE_SYMBOLS = 536 500 537 # The EXAMPLE_PATH tag can be used to specify one or more files or 501 538 # directories that contain example code fragments that are included (see 502 539 # the \include command). 503 540 504 EXAMPLE_PATH = ../examples ../ 541 EXAMPLE_PATH = ../examples \ 542 ../ 505 543 506 544 # If the value of the EXAMPLE_PATH tag contains directories, you can use the … … 556 594 # be generated. Documented entities will be cross-referenced with these sources. 557 595 # Note: To get rid of all source code in the generated output, make sure also 558 # VERBATIM_HEADERS is set to NO. 596 # VERBATIM_HEADERS is set to NO. If you have enabled CALL_GRAPH or CALLER_GRAPH 597 # then you must also enable this option. If you don't then doxygen will produce 598 # a warning and turn it on anyway 559 599 560 600 SOURCE_BROWSER = YES … … 582 622 583 623 REFERENCES_RELATION = YES 624 625 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 626 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 627 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 628 # link to the source code. Otherwise they will link to the documentstion. 629 630 REFERENCES_LINK_SOURCE = YES 584 631 585 632 # If the USE_HTAGS tag is set to YES then the references to source code … … 675 722 GENERATE_HTMLHELP = NO 676 723 724 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 725 # documentation will contain sections that can be hidden and shown after the 726 # page has loaded. For this to work a browser that supports 727 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 728 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). 729 730 HTML_DYNAMIC_SECTIONS = NO 731 677 732 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 678 733 # be used to specify the file name of the resulting .chm file. You … … 739 794 # generate Latex output. 740 795 741 GENERATE_LATEX = YES796 GENERATE_LATEX = NO 742 797 743 798 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. … … 1080 1135 CLASS_DIAGRAMS = YES 1081 1136 1137 # You can define message sequence charts within doxygen comments using the \msc 1138 # command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to 1139 # produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to 1140 # specify the directory where the mscgen tool resides. If left empty the tool is assumed to 1141 # be found in the default search path. 1142 1143 MSCGEN_PATH = 1144 1082 1145 # If set to YES, the inheritance and collaboration graphs will hide 1083 1146 # inheritance and usage relations if the target is undocumented … … 1137 1200 INCLUDED_BY_GRAPH = YES 1138 1201 1139 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will1202 # If the CALL_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will 1140 1203 # generate a call dependency graph for every global function or class method. 1141 1204 # Note that enabling this option will significantly increase the time of a run. … … 1145 1208 CALL_GRAPH = NO 1146 1209 1210 # If the CALLER_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will 1211 # generate a caller dependency graph for every global function or class method. 1212 # Note that enabling this option will significantly increase the time of a run. 1213 # So in most cases it will be better to enable caller graphs for selected 1214 # functions only using the \callergraph command. 1215 1216 CALLER_GRAPH = NO 1217 1147 1218 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 1148 1219 # will graphical hierarchy of all classes instead of a textual one. … … 1174 1245 DOTFILE_DIRS = 1175 1246 1176 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 1177 # (in pixels) of the graphs generated by dot. If a graph becomes larger than 1178 # this value, doxygen will try to truncate the graph, so that it fits within 1179 # the specified constraint. Beware that most browsers cannot cope with very 1180 # large images. 1181 1182 MAX_DOT_GRAPH_WIDTH = 1024 1183 1184 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 1185 # (in pixels) of the graphs generated by dot. If a graph becomes larger than 1186 # this value, doxygen will try to truncate the graph, so that it fits within 1187 # the specified constraint. Beware that most browsers cannot cope with very 1188 # large images. 1189 1190 MAX_DOT_GRAPH_HEIGHT = 1024 1247 # The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 1248 # nodes that will be shown in the graph. If the number of nodes in a graph 1249 # becomes larger than this value, doxygen will truncate the graph, which is 1250 # visualized by representing a node as a red box. Note that doxygen if the number 1251 # of direct children of the root node in a graph is already larger than 1252 # MAX_DOT_GRAPH_NOTES then the graph will not be shown at all. Also note 1253 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 1254 1255 DOT_GRAPH_MAX_NODES = 50 1191 1256 1192 1257 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the … … 1195 1260 # that lay further from the root node will be omitted. Note that setting this 1196 1261 # option to 1 or 2 may greatly reduce the computation time needed for large 1197 # code bases. Also note that a graph may be further truncated if the graph's 1198 # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH 1199 # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default), 1200 # the graph is not depth-constrained. 1262 # code bases. Also note that the size of a graph can be further restricted by 1263 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 1201 1264 1202 1265 MAX_DOT_GRAPH_DEPTH = 0 -
doc/user.cfg
r679441e rfed9433 1 # Doxyfile 1. 4.61 # Doxyfile 1.5.3-20071008 2 2 3 3 # This file describes the settings to be used by the documentation system … … 15 15 #--------------------------------------------------------------------------- 16 16 17 # This tag specifies the encoding used for all characters in the config file that 18 # follow. The default is UTF-8 which is also the encoding used for all text before 19 # the first occurrence of this tag. Doxygen uses libiconv (or the iconv built into 20 # libc) for the transcoding. See http://www.gnu.org/software/libiconv for the list of 21 # possible encodings. 22 23 DOXYFILE_ENCODING = UTF-8 24 17 25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded 18 26 # by quotes) that should identify the project. … … 24 32 # if some version control system is used. 25 33 26 #PROJECT_NUMBER = 0.3.0 34 PROJECT_NUMBER = 27 35 28 36 # The OUTPUT_DIRECTORY tag is used to specify the (relative or absolute) … … 46 54 # information to generate all constant output in the proper language. 47 55 # The default language is English, other supported languages are: 48 # Brazilian, Catalan, Chinese, Chinese-Traditional, Croatian, Czech, Danish,49 # Dutch, Finnish, French, German, Greek, Hungarian, Italian, Japanese,50 # Japanese-en (Japanese with English messages), Korean, Korean-en, Norwegian,51 # Polish, Portuguese, Romanian, Russian, Serbian, Slovak, Slovene, Spanish,52 # S wedish, and Ukrainian.56 # Afrikaans, Arabic, Brazilian, Catalan, Chinese, Chinese-Traditional, 57 # Croatian, Czech, Danish, Dutch, Finnish, French, German, Greek, Hungarian, 58 # Italian, Japanese, Japanese-en (Japanese with English messages), Korean, 59 # Korean-en, Lithuanian, Norwegian, Polish, Portuguese, Romanian, Russian, 60 # Serbian, Slovak, Slovene, Spanish, Swedish, and Ukrainian. 53 61 54 62 OUTPUT_LANGUAGE = English 55 56 # This tag can be used to specify the encoding used in the generated output.57 # The encoding is not always determined by the language that is chosen,58 # but also whether or not the output is meant for Windows or non-Windows users.59 # In case there is a difference, setting the USE_WINDOWS_ENCODING tag to YES60 # forces the Windows encoding (this is the default for the Windows binary),61 # whereas setting the tag to NO uses a Unix-style encoding (the default for62 # all platforms other than Windows).63 64 USE_WINDOWS_ENCODING = NO65 63 66 64 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will … … 107 105 # to NO the shortest path that makes the file name unique will be used. 108 106 109 FULL_PATH_NAMES = NO107 FULL_PATH_NAMES = YES 110 108 111 109 # If the FULL_PATH_NAMES tag is set to YES then the STRIP_FROM_PATH tag … … 116 114 # path to strip. 117 115 118 STRIP_FROM_PATH = 116 STRIP_FROM_PATH = ../src 119 117 120 118 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of … … 136 134 # will interpret the first line (until the first dot) of a JavaDoc-style 137 135 # comment as the brief description. If set to NO, the JavaDoc 138 # comments will behave just like the Qt-style comments (thus requiring an139 # explicit @brief command for a brief description.136 # comments will behave just like regular Qt-style comments 137 # (thus requiring an explicit @brief command for a brief description.) 140 138 141 139 JAVADOC_AUTOBRIEF = YES 140 141 # If the QT_AUTOBRIEF tag is set to YES then Doxygen will 142 # interpret the first line (until the first dot) of a Qt-style 143 # comment as the brief description. If set to NO, the comments 144 # will behave just like regular Qt-style comments (thus requiring 145 # an explicit \brief command for a brief description.) 146 147 QT_AUTOBRIEF = NO 142 148 143 149 # The MULTILINE_CPP_IS_BRIEF tag can be set to YES to make Doxygen … … 205 211 BUILTIN_STL_SUPPORT = NO 206 212 213 # If you use Microsoft's C++/CLI language, you should set this option to YES to 214 # enable parsing support. 215 216 CPP_CLI_SUPPORT = NO 217 218 # Set the SIP_SUPPORT tag to YES if your project consists of sip sources only. 219 # Doxygen will parse them like normal C++ but will assume all classes use public 220 # instead of private inheritance when no explicit protection keyword is present. 221 222 SIP_SUPPORT = NO 223 207 224 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC 208 225 # tag is set to YES, then doxygen will reuse the documentation of the first … … 253 270 254 271 EXTRACT_LOCAL_METHODS = NO 272 273 # If this flag is set to YES, the members of anonymous namespaces will be extracted 274 # and appear in the documentation as a namespace called 'anonymous_namespace{file}', 275 # where file will be replaced with the base name of the file that contains the anonymous 276 # namespace. By default anonymous namespace are hidden. 277 278 EXTRACT_ANON_NSPACES = NO 255 279 256 280 # If the HIDE_UNDOC_MEMBERS tag is set to YES, Doxygen will hide all … … 388 412 # in the documentation. The default is NO. 389 413 390 SHOW_DIRECTORIES = NO414 SHOW_DIRECTORIES = YES 391 415 392 416 # The FILE_VERSION_FILTER tag can be used to specify a program or script that … … 407 431 # by doxygen. Possible values are YES and NO. If left blank NO is used. 408 432 409 QUIET = YES433 QUIET = NO 410 434 411 435 # The WARNINGS tag can be used to turn on/off the warning messages that are … … 443 467 # be obtained via FILE_VERSION_FILTER) 444 468 445 WARN_FORMAT = "$file:$line: $text "469 WARN_FORMAT = "$file:$line: $text " 446 470 447 471 # The WARN_LOGFILE tag can be used to specify a file to which warning … … 461 485 462 486 INPUT = ../src 487 488 # This tag can be used to specify the character encoding of the source files that 489 # doxygen parses. Internally doxygen uses the UTF-8 encoding, which is also the default 490 # input encoding. Doxygen uses libiconv (or the iconv built into libc) for the transcoding. 491 # See http://www.gnu.org/software/libiconv for the list of possible encodings. 492 493 INPUT_ENCODING = UTF-8 463 494 464 495 # If the value of the INPUT tag contains directories, you can use the … … 475 506 # If left blank NO is used. 476 507 477 RECURSIVE = NO508 RECURSIVE = YES 478 509 479 510 # The EXCLUDE tag can be used to specify files and/or directories that should … … 497 528 EXCLUDE_PATTERNS = 498 529 530 # The EXCLUDE_SYMBOLS tag can be used to specify one or more symbol names 531 # (namespaces, classes, functions, etc.) that should be excluded from the output. 532 # The symbol name can be a fully qualified name, a word, or if the wildcard * is used, 533 # a substring. Examples: ANamespace, AClass, AClass::ANamespace, ANamespace::*Test 534 535 EXCLUDE_SYMBOLS = 536 499 537 # The EXAMPLE_PATH tag can be used to specify one or more files or 500 538 # directories that contain example code fragments that are included (see 501 539 # the \include command). 502 540 503 EXAMPLE_PATH = ../examples ../ 541 EXAMPLE_PATH = ../examples \ 542 ../ 504 543 505 544 # If the value of the EXAMPLE_PATH tag contains directories, you can use the … … 555 594 # be generated. Documented entities will be cross-referenced with these sources. 556 595 # Note: To get rid of all source code in the generated output, make sure also 557 # VERBATIM_HEADERS is set to NO. 558 559 SOURCE_BROWSER = NO 596 # VERBATIM_HEADERS is set to NO. If you have enabled CALL_GRAPH or CALLER_GRAPH 597 # then you must also enable this option. If you don't then doxygen will produce 598 # a warning and turn it on anyway 599 600 SOURCE_BROWSER = YES 560 601 561 602 # Setting the INLINE_SOURCES tag to YES will include the body … … 581 622 582 623 REFERENCES_RELATION = YES 624 625 # If the REFERENCES_LINK_SOURCE tag is set to YES (the default) 626 # and SOURCE_BROWSER tag is set to YES, then the hyperlinks from 627 # functions in REFERENCES_RELATION and REFERENCED_BY_RELATION lists will 628 # link to the source code. Otherwise they will link to the documentstion. 629 630 REFERENCES_LINK_SOURCE = YES 583 631 584 632 # If the USE_HTAGS tag is set to YES then the references to source code … … 674 722 GENERATE_HTMLHELP = NO 675 723 724 # If the HTML_DYNAMIC_SECTIONS tag is set to YES then the generated HTML 725 # documentation will contain sections that can be hidden and shown after the 726 # page has loaded. For this to work a browser that supports 727 # JavaScript and DHTML is required (for instance Mozilla 1.0+, Firefox 728 # Netscape 6.0+, Internet explorer 5.0+, Konqueror, or Safari). 729 730 HTML_DYNAMIC_SECTIONS = NO 731 676 732 # If the GENERATE_HTMLHELP tag is set to YES, the CHM_FILE tag can 677 733 # be used to specify the file name of the resulting .chm file. You … … 738 794 # generate Latex output. 739 795 740 GENERATE_LATEX = NO 796 GENERATE_LATEX = NO 741 797 742 798 # The LATEX_OUTPUT tag is used to specify where the LaTeX docs will be put. … … 1079 1135 CLASS_DIAGRAMS = YES 1080 1136 1137 # You can define message sequence charts within doxygen comments using the \msc 1138 # command. Doxygen will then run the mscgen tool (see http://www.mcternan.me.uk/mscgen/) to 1139 # produce the chart and insert it in the documentation. The MSCGEN_PATH tag allows you to 1140 # specify the directory where the mscgen tool resides. If left empty the tool is assumed to 1141 # be found in the default search path. 1142 1143 MSCGEN_PATH = 1144 1081 1145 # If set to YES, the inheritance and collaboration graphs will hide 1082 1146 # inheritance and usage relations if the target is undocumented … … 1136 1200 INCLUDED_BY_GRAPH = YES 1137 1201 1138 # If the CALL_GRAPH and HAVE_DOT tags are set to YES then doxygen will1202 # If the CALL_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will 1139 1203 # generate a call dependency graph for every global function or class method. 1140 1204 # Note that enabling this option will significantly increase the time of a run. … … 1144 1208 CALL_GRAPH = NO 1145 1209 1210 # If the CALLER_GRAPH, SOURCE_BROWSER and HAVE_DOT tags are set to YES then doxygen will 1211 # generate a caller dependency graph for every global function or class method. 1212 # Note that enabling this option will significantly increase the time of a run. 1213 # So in most cases it will be better to enable caller graphs for selected 1214 # functions only using the \callergraph command. 1215 1216 CALLER_GRAPH = NO 1217 1146 1218 # If the GRAPHICAL_HIERARCHY and HAVE_DOT tags are set to YES then doxygen 1147 1219 # will graphical hierarchy of all classes instead of a textual one. … … 1173 1245 DOTFILE_DIRS = 1174 1246 1175 # The MAX_DOT_GRAPH_WIDTH tag can be used to set the maximum allowed width 1176 # (in pixels) of the graphs generated by dot. If a graph becomes larger than 1177 # this value, doxygen will try to truncate the graph, so that it fits within 1178 # the specified constraint. Beware that most browsers cannot cope with very 1179 # large images. 1180 1181 MAX_DOT_GRAPH_WIDTH = 1024 1182 1183 # The MAX_DOT_GRAPH_HEIGHT tag can be used to set the maximum allows height 1184 # (in pixels) of the graphs generated by dot. If a graph becomes larger than 1185 # this value, doxygen will try to truncate the graph, so that it fits within 1186 # the specified constraint. Beware that most browsers cannot cope with very 1187 # large images. 1188 1189 MAX_DOT_GRAPH_HEIGHT = 1024 1247 # The MAX_DOT_GRAPH_MAX_NODES tag can be used to set the maximum number of 1248 # nodes that will be shown in the graph. If the number of nodes in a graph 1249 # becomes larger than this value, doxygen will truncate the graph, which is 1250 # visualized by representing a node as a red box. Note that doxygen if the number 1251 # of direct children of the root node in a graph is already larger than 1252 # MAX_DOT_GRAPH_NOTES then the graph will not be shown at all. Also note 1253 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH. 1254 1255 DOT_GRAPH_MAX_NODES = 50 1190 1256 1191 1257 # The MAX_DOT_GRAPH_DEPTH tag can be used to set the maximum depth of the … … 1194 1260 # that lay further from the root node will be omitted. Note that setting this 1195 1261 # option to 1 or 2 may greatly reduce the computation time needed for large 1196 # code bases. Also note that a graph may be further truncated if the graph's 1197 # image dimensions are not sufficient to fit the graph (see MAX_DOT_GRAPH_WIDTH 1198 # and MAX_DOT_GRAPH_HEIGHT). If 0 is used for the depth value (the default), 1199 # the graph is not depth-constrained. 1262 # code bases. Also note that the size of a graph can be further restricted by 1263 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction. 1200 1264 1201 1265 MAX_DOT_GRAPH_DEPTH = 0
Note: See TracChangeset
for help on using the changeset viewer.
