Lines Matching full:in
6 # All text after a double hash (##) is considered a comment and is placed in
20 # This tag specifies the encoding used for all characters in the config file
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.
50 # in the documentation. The maximum height of the logo should not exceed 55
64 # directories (in 2 levels) under the output directory of each output format and
67 # putting all generated files in the same directory would otherwise causes
74 # characters to appear in the names of generated files. If set to NO, non-ASCII
81 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
83 # information to generate all constant output in the proper language.
97 # descriptions after the members that are listed in the file and class
113 # used to form the text in various listings. Each string in this list, if found
141 # inherited members of a class in the documentation of that class as if those
149 # before files name in the file list and in the header files. If set to NO the
157 # part of the path. The tag can be used to show relative paths in the file list.
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
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.
231 # This tag can be used to specify a number of aliases that act as commands in
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
245 # will allow you to use the command class in the itcl::class meaning.
279 # extension. Doxygen has a built-in mapping, but you can override or extend it
284 # Fortran. In the later case the parser tries to guess whether the code is fixed
300 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
307 # to that level are automatically included in the table of contents, even if
317 # be prevented in individual cases by putting a % sign in front of the word or
325 # tag to YES in order to let doxygen match functions declarations and
349 # doxygen to replace the get and set methods by a property in the documentation.
357 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
359 # member in the group (if any) for the other members of the group. By default
382 # are shown inside the group in which they are included (e.g. using \ingroup)
386 # Note that this feature does not work in combination with
393 # with only public data fields or simple typedef fields will be shown inline in
394 # the documentation of the scope in which they are defined (i.e. file,
404 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
407 # useful for C code in case the coding convention dictates that all compound
415 # an expensive process and often the same symbol appears multiple times in the
430 # If the EXTRACT_ALL tag is set to YES, doxygen will assume all entities in
441 # be included in the documentation.
447 # scope will be included in the documentation.
453 # included in the documentation.
459 # locally in source files will be included in the documentation. If set to NO,
460 # only classes defined in header files are included. Does not have any effect
467 # which are defined in the implementation section but not in the interface are
468 # included in the documentation. If set to NO, only methods in the interface are
475 # extracted and appear in the documentation as a namespace called
485 # members will be included in the various overviews, but no documentation
492 # undocumented classes that are normally visible in the class hierarchy. If set
493 # to NO, these classes will be included in the various overviews. This option
501 # included in the documentation.
521 # names in lower-case letters. If set to YES, upper-case letters are also
523 # in case and if your file system supports case sensitive file names. Windows
530 # their full class and namespace scopes in the documentation. If set to YES, the
544 # the files that are included by a file in the documentation of that file.
551 # which file to include in order to use the member.
557 # files with double quotes in the documentation rather than with sharp brackets.
562 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
570 # name. If set to NO, the members will appear in declaration order.
577 # name. If set to NO, the members will appear in declaration order. Note that
578 # this will also influence the order of the classes in the class list.
585 # destructors are listed first. If set to NO the constructors will appear in the
597 # appear in their defined order.
617 # accept a match between prototype and implementation in such cases.
623 # list. This list is created by putting \todo commands in the documentation.
629 # list. This list is created by putting \test commands in the documentation.
635 # list. This list is created by putting \bug commands in the documentation.
641 # the deprecated list. This list is created by putting \deprecated commands in
654 # initial value of a variable or macro / define can have for it to appear in the
658 # controlled using \showinitializer or \hideinitializer command in the
697 # output files in an output format independent way. To create the layout file
713 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
746 # potential errors in the documentation, such as not documenting some parameters
747 # in a documented function, or documenting parameters that don't exist or using
806 # *.h) to filter out the source-files in the directories.
874 # *.h) to filter out the source-files in the directories. If left blank all
887 # that contain images that are to be included in the documentation (see the
955 # Note: To get rid of all source code in the generated output, make sure that
987 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
994 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1005 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1012 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1016 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1017 # tools must be available from the command line (i.e. in the search path).
1037 # rich C++ code for which doxygen's built-in parser lacks the necessary type
1064 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1071 # In case all classes in a project start with a common prefix, all classes will
1072 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1089 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1139 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1152 # style sheet in the list overrules the setting of the previous ones in the
1161 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1162 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1169 # will adjust the colors in the style sheet and background images according to
1180 # in the HTML output. For a value of 0 the output will use grayscales only. A
1188 # luminance component of the colors in the HTML output. Values below 100
1216 # shown in the various tree structured indices initially; the user can expand
1221 # representing an infinite number of entries and will result in a full expanded
1232 # Makefile in the HTML output directory. Running make will produce the docset in
1233 # that directory and running make install will install the docset in
1281 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1283 # words in the documentation. The HTML workshop also contains a viewer for
1291 # file. You can add a path in front of the file if the result should not be
1306 # (YES) or that it should be included in the master .chm file (NO).
1319 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1398 # install this plugin and make it available under the help contents menu in
1420 # it. Since the tabs in the index contain the same information as the navigation
1445 # doxygen will group on one line in the generated HTML documentation.
1448 # in the overview section.
1455 # to set the initial width (in pixels) of the frame in which the tree is shown.
1462 # external symbols imported via tag files in a separate window.
1468 # Use this tag to change the font size of LaTeX formulas included as images in
1481 # Note that when changing this option you need to delete any form_*.png files in
1491 # installed or if you want to formulas look prettier in the HTML output. When
1607 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1633 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1644 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1660 # trees in general.
1676 # that should be included in the LaTeX output. The package can be specified just
1719 # style sheet in the list overrules the setting of the previous ones in the
1753 # when generating formulas in HTML.
1760 # index chapters (such as File Index, Compound Index, etc.) in the output.
1767 # code with syntax highlighting in the LaTeX output.
1804 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1813 # trees in general.
1841 # Set optional variables used in the generation of an RTF document. Syntax is
1849 # with syntax highlighting in the RTF output.
1869 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1878 # man pages. In case the manual section does not start with a number, the number
1887 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1894 # will generate one additional man file for each entity documented in the real
1913 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1940 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1998 # The names of the make variables in the generated doxyrules.make file are
1999 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2011 # C-preprocessor directives found in the sources and include files.
2017 # in the source code. If set to NO, only conditional compilation will be
2018 # performed. Macro expansion can be done in a controlled way by setting
2033 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
2048 # patterns (like *.h and *.hpp) to filter out the header-files in the
2067 # macro definition that is found in the sources will be used. Use the PREDEFINED
2069 # definition found in the source code.
2098 # the path). If a tag file is not located in the directory in which doxygen is
2109 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2117 # in the modules index. If set to NO, only the current project's groups will be
2123 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2141 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2151 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2153 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2158 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2159 # then run dia to produce the diagram and insert it in the documentation. The
2161 # If left empty dia is assumed to be found in the default search path.
2174 # Bell Labs. The other options in this section have no effect if this option is
2181 # to run in parallel. When set to 0 doxygen will base this on the number of
2182 # processors available in the system. You can set it explicitly to a value
2190 # When you want a differently looking font in the dot files that doxygen
2192 # sure dot is able to find the font, which can be done by putting it in a
2200 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2239 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2289 # So in most cases it will be better to enable call graphs for selected
2301 # So in most cases it will be better to enable caller graphs for selected
2317 # dependencies a directory has on other directories in a graphical way. The
2319 # files in the directories.
2327 # output formats in the documentation of the dot tool (Graphviz (see:
2329 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2330 # to make the SVG files visible in IE 9+ (other browsers do not have this
2347 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2355 # found. If left blank, it is assumed the dot tool can be found in the path.
2361 # contain dot files that are included in the documentation (see the \dotfile
2368 # contain msc files that are included in the documentation (see the \mscfile
2374 # contain dia files that are included in the documentation (see the \diafile
2382 # generate a warning when it encounters a \startuml command in this case and
2393 # the !include statement in a plantuml block.
2398 # that will be shown in the graph. If the number of nodes in a graph becomes
2401 # children of the root node in a graph is already larger than
2434 # files in one run (i.e. multiple -o and -T options on the command line). This
2443 # explaining the meaning of the various boxes and arrows in the dot generated