Lines Matching +full:cancel +full:- +full:in +full:- +full:progress

6 # All text after a double hash (##) is considered a comment and is placed in
16 #---------------------------------------------------------------------------
18 #---------------------------------------------------------------------------
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
25 # The default value is: UTF-8.
27 DOXYFILE_ENCODING      = UTF-8
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.
50 # in the documentation. The maximum height of the logo should not exceed 55
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
67 # putting all generated files in the same directory would otherwise causes
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
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.
85 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
87 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
88 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
90 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
97 # descriptions after the members that are listed in the file and class
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
116 # text. Otherwise, the brief description is used as-is. If left blank, the
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
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.
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
172 # using the -I flag.
178 # support long names like on DOS, Mac, or CD-ROM.
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-
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
201 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
203 # to treat a multi-line C++ comment block as a detailed description. Set this
213 # documentation from any documented member that it re-implements.
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
243 # This tag can be used to specify a number of word-keyword mappings (TCL only).
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
282 # C#, C, C++, D, PHP, Objective-C, Python, Fortran (fixed format Fortran:
284 # Fortran. In the later case the parser tries to guess whether the code is fixed
296 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
300 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
306 # When the TOC_INCLUDE_HEADINGS tag is set to a non-zero value, all headings up
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
416 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
426 #---------------------------------------------------------------------------
428 #---------------------------------------------------------------------------
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
466 # This flag is only useful for Objective-C code. If set to YES, local methods,
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.
603 # fully-qualified names, including namespaces. If set to NO, the class list will
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
688 # popen()) the command input-file, where command is the value of the
689 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
697 # output files in an output format independent way. To create the layout file
698 # that represents doxygen's defaults, run doxygen with the -l option. You can
713 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
718 #---------------------------------------------------------------------------
719 # Configuration options related to warning and progress messages
720 #---------------------------------------------------------------------------
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
783 #---------------------------------------------------------------------------
785 #---------------------------------------------------------------------------
796 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
800 # The default value is: UTF-8.
802 INPUT_ENCODING         = UTF-8
806 # *.h) to filter out the source-files in the directories.
875 # *.h) to filter out the source-files in the directories. If left blank all
888 # that contain images that are to be included in the documentation (see the
897 # <filter> <input-file>
899 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
949 #---------------------------------------------------------------------------
951 #---------------------------------------------------------------------------
954 # generated. Documented entities will be cross-referenced with these sources.
956 # Note: To get rid of all source code in the generated output, make sure that
988 # to YES then the hyperlinks from functions in REFERENCES_RELATION and
995 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1006 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1012 # - Install the latest version of global
1013 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1014 # - Make sure the INPUT points to the root of the source tree
1015 # - Run doxygen as normal
1017 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1018 # tools must be available from the command line (i.e. in the search path).
1038 # rich C++ code for which doxygen's built-in parser lacks the necessary type
1041 # generated with the -Duse-libclang=ON option for CMake.
1054 #---------------------------------------------------------------------------
1056 #---------------------------------------------------------------------------
1065 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1072 # In case all classes in a project start with a common prefix, all classes will
1073 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1080 #---------------------------------------------------------------------------
1082 #---------------------------------------------------------------------------
1090 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1104 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1112 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1124 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1134 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1135 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1140 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1146 # The HTML_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1153 # style sheet in the list overrules the setting of the previous ones in the
1162 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1163 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1164 # files will be copied as-is; there are no commands or markers available.
1170 # will adjust the colors in the style sheet and background images according to
1181 # in the HTML output. For a value of 0 the output will use grayscales only. A
1189 # luminance component of the colors in the HTML output. Values below 100
1217 # shown in the various tree structured indices initially; the user can expand
1222 # representing an infinite number of entries and will result in a full expanded
1233 # Makefile in the HTML output directory. Running make will produce the docset in
1234 # that directory and running make install will install the docset in
1252 # set bundle. This should be a reverse domain-name style string, e.g.
1260 # the documentation publisher. This should be a reverse domain-name style
1276 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1282 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1284 # words in the documentation. The HTML workshop also contains a viewer for
1292 # file. You can add a path in front of the file if the result should not be
1299 # including file name) of the HTML help compiler (hhc.exe). If non-empty,
1307 # (YES) or that it should be included in the master .chm file (NO).
1320 # (YES) or a normal table of contents (NO) in the .chm file. Furthermore it
1352 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1360 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1369 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1377 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1385 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1391 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1399 # install this plugin and make it available under the help contents menu in
1421 # it. Since the tabs in the index contain the same information as the navigation
1428 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1430 # value is set to YES, a side panel will be generated containing a tree-like
1435 # further fine-tune the look of the index. As an example, the default style
1446 # doxygen will group on one line in the generated HTML documentation.
1449 # in the overview section.
1456 # to set the initial width (in pixels) of the frame in which the tree is shown.
1463 # external symbols imported via tag files in a separate window.
1469 # Use this tag to change the font size of LaTeX formulas included as images in
1482 # Note that when changing this option you need to delete any form_*.png files in
1491 # instead of using pre-rendered bitmaps. Use this if you do not have LaTeX
1492 # installed or if you want to formulas look prettier in the HTML output. When
1503 # Possible values are: HTML-CSS (which is slower, but has the best
1505 # The default value is: HTML-CSS.
1508 MATHJAX_FORMAT         = HTML-CSS
1549 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1552 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1608 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1624 #---------------------------------------------------------------------------
1626 #---------------------------------------------------------------------------
1634 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1645 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1661 # trees in general.
1677 # that should be included in the LaTeX output. The package can be specified just
1694 # Note: Only use a user-defined header if you know what you are doing! The
1710 # Note: Only use a user-defined footer if you know what you are doing!
1715 # The LATEX_EXTRA_STYLESHEET tag can be used to specify additional user-defined
1720 # style sheet in the list overrules the setting of the previous ones in the
1728 # directory. Note that the files will be copied as-is; there are no commands or
1754 # when generating formulas in HTML.
1761 # index chapters (such as File Index, Compound Index, etc.) in the output.
1768 # code with syntax highlighting in the LaTeX output.
1793 #---------------------------------------------------------------------------
1795 #---------------------------------------------------------------------------
1805 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1814 # trees in general.
1842 # Set optional variables used in the generation of an RTF document. Syntax is
1844 # using doxygen -e rtf extensionFile.
1850 # with syntax highlighting in the RTF output.
1859 #---------------------------------------------------------------------------
1861 #---------------------------------------------------------------------------
1870 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1879 # man pages. In case the manual section does not start with a number, the number
1888 # MAN_OUTPUT in which the man pages are placed. If defaults to man followed by
1895 # will generate one additional man file for each entity documented in the real
1903 #---------------------------------------------------------------------------
1905 #---------------------------------------------------------------------------
1914 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1922 # listings (including syntax highlighting and cross-referencing information) to
1930 #---------------------------------------------------------------------------
1932 #---------------------------------------------------------------------------
1941 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1949 # program listings (including syntax highlighting and cross-referencing
1957 #---------------------------------------------------------------------------
1959 #---------------------------------------------------------------------------
1969 #---------------------------------------------------------------------------
1971 #---------------------------------------------------------------------------
1999 # The names of the make variables in the generated doxyrules.make file are
2000 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
2007 #---------------------------------------------------------------------------
2009 #---------------------------------------------------------------------------
2012 # C-preprocessor directives found in the sources and include files.
2018 # in the source code. If set to NO, only conditional compilation will be
2019 # performed. Macro expansion can be done in a controlled way by setting
2034 # If the SEARCH_INCLUDES tag is set to YES, the include files in the
2049 # patterns (like *.h and *.hpp) to filter out the header-files in the
2057 # defined before the preprocessor is started (similar to the -D option of e.g.
2068 # macro definition that is found in the sources will be used. Use the PREDEFINED
2070 # definition found in the source code.
2076 # remove all references to function-like macros that are alone on a line, have
2078 # are typically used for boiler-plate code, and will confuse the parser if not
2085 #---------------------------------------------------------------------------
2087 #---------------------------------------------------------------------------
2099 # the path). If a tag file is not located in the directory in which doxygen is
2110 # If the ALLEXTERNALS tag is set to YES, all external class will be listed in
2118 # in the modules index. If set to NO, only the current project's groups will be
2124 # If the EXTERNAL_PAGES tag is set to YES, all external pages will be listed in
2137 #---------------------------------------------------------------------------
2139 #---------------------------------------------------------------------------
2142 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2152 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2154 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2159 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2160 # then run dia to produce the diagram and insert it in the documentation. The
2162 # If left empty dia is assumed to be found in the default search path.
2175 # Bell Labs. The other options in this section have no effect if this option is
2182 # to run in parallel. When set to 0 doxygen will base this on the number of
2183 # processors available in the system. You can set it explicitly to a value
2191 # When you want a differently looking font in the dot files that doxygen
2193 # sure dot is able to find the font, which can be done by putting it in a
2201 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2240 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2290 # So in most cases it will be better to enable call graphs for selected
2302 # So in most cases it will be better to enable caller graphs for selected
2318 # dependencies a directory has on other directories in a graphical way. The
2320 # files in the directories.
2328 # output formats in the documentation of the dot tool (Graphviz (see:
2330 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2331 # to make the SVG files visible in IE 9+ (other browsers do not have this
2348 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2356 # found. If left blank, it is assumed the dot tool can be found in the path.
2362 # contain dot files that are included in the documentation (see the \dotfile
2369 # contain msc files that are included in the documentation (see the \mscfile
2375 # contain dia files that are included in the documentation (see the \diafile
2383 # generate a warning when it encounters a \startuml command in this case and
2394 # the !include statement in a plantuml block.
2399 # that will be shown in the graph. If the number of nodes in a graph becomes
2402 # children of the root node in a graph is already larger than
2427 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2435 # files in one run (i.e. multiple -o and -T options on the command line). This
2444 # explaining the meaning of the various boxes and arrows in the dot generated