Lines Matching +full:cancel +full:- +full:in +full:- +full:progress
7 # Redistribution and use in source and binary forms, with or without
11 # 2. Redistributions in binary form must reproduce the above copyright
12 # notice, this list of conditions and the following disclaimer in the
21 # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
25 # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27 # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
35 # This was initially autogenerated 'doxywizard' and then hand-tuned.
51 #---------------------------------------------------------------------------
53 #---------------------------------------------------------------------------
55 # This tag specifies the encoding used for all characters in the config file
56 # that follow. The default is UTF-8 which is also the encoding used for all text
60 # The default value is: UTF-8.
62 DOXYFILE_ENCODING = UTF-8
65 # double-quotes, unless you are using Doxywizard) that should identify the
66 # project for which the documentation is generated. This name is used in the
67 # title of most generated pages and in a few other places.
84 # With the PROJECT_LOGO tag one can specify an logo or icon that is included in
89 PROJECT_LOGO = @abs_srcdir@/images/Open-Thread-Logo-200x42.png
98 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
99 # directories (in 2 levels) under the output directory of each output format and
102 # putting all generated files in the same directory would otherwise causes
108 # The OUTPUT_LANGUAGE tag is used to specify the language in which all
110 # information to generate all constant output in the proper language.
112 # Chinese-Traditional, Croatian, Czech, Danish, Dutch, English (United States),
114 # Indonesian, Italian, Japanese, Japanese-en (Japanese with English messages),
115 # Korean, Korean-en (Korean with English messages), Latvian, Lithuanian,
117 # Serbian, Serbian-Cyrillic, Slovak, Slovene, Spanish, Swedish, Turkish,
124 # descriptions after the members that are listed in the file and class
139 # This tag implements a quasi-intelligent brief description abbreviator that is
140 # used to form the text in various listings. Each string in this list, if found
143 # text. Otherwise, the brief description is used as-is. If left blank, the
168 # inherited members of a class in the documentation of that class as if those
176 # before files name in the file list and in the header files. If set to NO the
182 # The STRIP_FROM_PATH tag can be used to strip a user-defined part of the path.
183 # Stripping is only done if one of the specified strings matches the left-hand
184 # part of the path. The tag can be used to show relative paths in the file list.
195 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of the
196 # path mentioned in the documentation of a class, which tells the reader which
197 # header file to include in order to use a class. If left blank only the name of
200 # using the -I flag.
206 # support long names like on DOS, Mac, or CD-ROM.
212 # first line (until the first dot) of a Javadoc-style comment as the brief
213 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
221 # line (until the first dot) of a Qt-style comment as the brief description. If
222 # set to NO, the Qt-style will behave just like regular Qt-style comments (thus
229 # multi-line C++ special comment block (i.e. a block of //! or /// comments) as
231 # to treat a multi-line C++ comment block as a detailed description. Set this
241 # documentation from any documented member that it re-implements.
253 # The TAB_SIZE tag can be used to set the number of spaces in a tab. Doxygen
254 # uses this value to replace tabs by spaces in code fragments.
259 # This tag can be used to specify a number of aliases that act as commands in
264 # will allow you to put the command \sideeffect (or @sideeffect) in the
265 # documentation, which will result in a user-defined paragraph with heading
266 # "Side Effects:". You can put \n's in the value part of an alias to insert
271 # This tag can be used to specify a number of word-keyword mappings (TCL only).
273 # will allow you to use the command class in the itcl::class meaning.
307 # extension. Doxygen has a built-in mapping, but you can override or extend it
310 # C#, C, C++, D, PHP, Objective-C, Python, Fortran, VHDL. For instance to make
321 # If the MARKDOWN_SUPPORT tag is enabled then doxygen pre-processes all comments
325 # mix doxygen, HTML, and XML commands with Markdown formatting. Disable only in
333 # be prevented in individual cases by by putting a % sign in front of the word
341 # tag to YES in order to let doxygen match functions declarations and
365 # doxygen to replace the get and set methods by a property in the documentation.
373 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
375 # member in the group (if any) for the other members of the group. By default
391 # are shown inside the group in which they are included (e.g. using \ingroup)
395 # Note that this feature does not work in combination with
402 # with only public data fields or simple typedef fields will be shown inline in
403 # the documentation of the scope in which they are defined (i.e. file,
413 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
416 # useful for C code in case the coding convention dictates that all compound
424 # an expensive process and often the same symbol appears multiple times in the
425 # code, doxygen keeps a cache of pre-resolved symbols. If the cache is too small
435 #---------------------------------------------------------------------------
437 #---------------------------------------------------------------------------
439 # If the EXTRACT_ALL tag is set to YES doxygen will assume all entities in
450 # be included in the documentation.
456 # scope will be included in the documentation.
462 # included in the documentation.
468 # locally in source files will be included in the documentation. If set to NO
469 # only classes defined in header files are included. Does not have any effect
475 # This flag is only useful for Objective-C code. When set to YES local methods,
476 # which are defined in the implementation section but not in the interface are
477 # included in the documentation. If set to NO only methods in the interface are
484 # extracted and appear in the documentation as a namespace called
494 # members will be included in the various overviews, but no documentation
501 # undocumented classes that are normally visible in the class hierarchy. If set
502 # to NO these classes will be included in the various overviews. This option has
510 # included in the documentation.
530 # names in lower-case letters. If set to YES upper-case letters are also
532 # in case and if your file system supports case sensitive file names. Windows
539 # their full class and namespace scopes in the documentation. If set to YES the
546 # the files that are included by a file in the documentation of that file.
553 # which file to include in order to use the member.
559 # files with double quotes in the documentation rather than with sharp brackets.
564 # If the INLINE_INFO tag is set to YES then a tag [inline] is inserted in the
572 # name. If set to NO the members will appear in declaration order.
579 # name. If set to NO the members will appear in declaration order. Note that
580 # this will also influence the order of the classes in the class list.
587 # destructors are listed first. If set to NO the constructors will appear in the
599 # appear in their defined order.
605 # fully-qualified names, including namespaces. If set to NO, the class list will
619 # accept a match between prototype and implementation in such cases.
625 # todo list. This list is created by putting \todo commands in the
632 # test list. This list is created by putting \test commands in the
639 # list. This list is created by putting \bug commands in the documentation.
645 # the deprecated list. This list is created by putting \deprecated commands in
658 # initial value of a variable or macro / define can have for it to appear in the
662 # controlled using \showinitializer or \hideinitializer command in the
692 # popen()) the command command input-file, where command is the value of the
693 # FILE_VERSION_FILTER tag, and input-file is the name of an input file provided
701 # output files in an output format independent way. To create the layout file
702 # that represents doxygen's defaults, run doxygen with the -l option. You can
717 # LATEX_BIB_STYLE. To use this feature you need bibtex and perl available in the
723 #---------------------------------------------------------------------------
724 # Configuration options related to warning and progress messages
725 #---------------------------------------------------------------------------
751 # potential errors in the documentation, such as not documenting some parameters
752 # in a documented function, or documenting parameters that don't exist or using
782 #---------------------------------------------------------------------------
784 #---------------------------------------------------------------------------
798 # that doxygen parses. Internally doxygen uses the UTF-8 encoding. Doxygen uses
802 # The default value is: UTF-8.
804 INPUT_ENCODING = UTF-8
808 # *.h) to filter out the source-files in the directories. If left blank the
861 EXCLUDE = ../src/ncp/ncp.pb-c.h \
862 ../src/ncp/ncp.pb-c.c
899 # *.h) to filter out the source-files in the directories. If left blank all
912 # that contain images that are to be included in the documentation (see the
921 # <filter> <input-file>
923 # where <filter> is the value of the INPUT_FILTER tag, and <input-file> is the
965 #---------------------------------------------------------------------------
967 #---------------------------------------------------------------------------
970 # generated. Documented entities will be cross-referenced with these sources.
972 # Note: To get rid of all source code in the generated output, make sure that
1004 # to YES, then the hyperlinks from functions in REFERENCES_RELATION and
1011 # If SOURCE_TOOLTIPS is enabled (the default) then hovering a hyperlink in the
1022 # point to the HTML generated by the htags(1) tool instead of doxygen built-in
1028 # - Install the latest version of global
1029 # - Enable SOURCE_BROWSER and USE_HTAGS in the config file
1030 # - Make sure the INPUT points to the root of the source tree
1031 # - Run doxygen as normal
1033 # Doxygen will invoke htags (and that will in turn invoke gtags), so these
1034 # tools must be available from the command line (i.e. in the search path).
1051 #---------------------------------------------------------------------------
1053 #---------------------------------------------------------------------------
1062 # The COLS_IN_ALPHA_INDEX tag can be used to specify the number of columns in
1069 # In case all classes in a project start with a common prefix, all classes will
1070 # be put under the same header in the alphabetical index. The IGNORE_PREFIX tag
1077 #---------------------------------------------------------------------------
1079 #---------------------------------------------------------------------------
1087 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1101 # The HTML_HEADER tag can be used to specify a user-defined HTML header file for
1109 # doxygen -w html new_header.html new_footer.html new_stylesheet.css
1121 # The HTML_FOOTER tag can be used to specify a user-defined HTML footer for each
1131 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading style
1132 # sheet that is used by each HTML page. It can be used to fine-tune the look of
1137 # it is more robust and this tag (HTML_STYLESHEET) will in the future become
1143 # The HTML_EXTRA_STYLESHEET tag can be used to specify an additional user-
1157 # $relpath^ marker in the HTML_HEADER and/or HTML_FOOTER files to load these
1158 # files. In the HTML_STYLESHEET file, use the file name only. Also note that the
1159 # files will be copied as-is; there are no commands or markers available.
1165 # will adjust the colors in the stylesheet and background images according to
1176 # in the HTML output. For a value of 0 the output will use grayscales only. A
1184 # luminance component of the colors in the HTML output. Values below 100
1211 # shown in the various tree structured indices initially; the user can expand
1216 # representing an infinite number of entries and will result in a full expanded
1227 # Makefile in the HTML output directory. Running make will produce the docset in
1228 # that directory and running make install will install the docset in
1246 # set bundle. This should be a reverse domain-name style string, e.g.
1254 # the documentation publisher. This should be a reverse domain-name style
1270 # (see: http://www.microsoft.com/en-us/download/details.aspx?id=21138) on
1276 # Windows help format (.hlp) on all Windows platforms in the future. Compressed
1278 # words in the documentation. The HTML workshop also contains a viewer for
1286 # file. You can add a path in front of the file if the result should not be
1293 # including file name) of the HTML help compiler ( hhc.exe). If non-empty
1301 # YES) or that it should be included in the master .chm file ( NO).
1314 # YES) or a normal table of contents ( NO) in the .chm file.
1345 # (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#namespace).
1353 # Folders (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#virtual-
1362 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1370 # Filters (see: http://qt-project.org/doc/qt-4.8/qthelpproject.html#custom-
1378 # http://qt-project.org/doc/qt-4.8/qthelpproject.html#filter-attributes).
1384 # qhelpgenerator. If non-empty doxygen will try to run qhelpgenerator on the
1392 # install this plugin and make it available under the help contents menu in
1414 # it. Since the tabs in the index contain the same information as the navigation
1421 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1423 # value is set to YES, a side panel will be generated containing a tree-like
1428 # further fine-tune the look of the index. As an example, the default style
1439 # doxygen will group on one line in the generated HTML documentation.
1442 # in the overview section.
1449 # to set the initial width (in pixels) of the frame in which the tree is shown.
1456 # external symbols imported via tag files in a separate window.
1462 # Use this tag to change the font size of LaTeX formulas included as images in
1475 # Note that when changing this option you need to delete any form_*.png files in
1485 # installed or if you want to formulas look prettier in the HTML output. When
1496 # Possible values are: HTML-CSS (which is slower, but has the best
1498 # The default value is: HTML-CSS.
1501 MATHJAX_FORMAT = HTML-CSS
1542 # using the <cursor keys>. Press <Enter> to select an item or <escape> to cancel
1545 # to select a filter and <Enter> or <escape> to activate or cancel the filter
1601 # useful in combination with EXTRA_SEARCH_MAPPINGS to search through multiple
1617 #---------------------------------------------------------------------------
1619 #---------------------------------------------------------------------------
1627 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1638 # bitmaps for formulas in the HTML output, but not in the Makefile that is
1654 # trees in general.
1670 # that should be included in the LaTeX output. To get the times font for
1684 # Note: Only use a user-defined header if you know what you are doing! The
1698 # Note: Only use a user-defined footer if you know what you are doing!
1705 # directory. Note that the files will be copied as-is; there are no commands or
1731 # when generating formulas in HTML.
1738 # index chapters (such as File Index, Compound Index, etc.) in the output.
1745 # code with syntax highlighting in the LaTeX output.
1762 #---------------------------------------------------------------------------
1764 #---------------------------------------------------------------------------
1774 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1783 # trees in general.
1811 # Set optional variables used in the generation of an RTF document. Syntax is
1813 # using doxygen -e rtf extensionFile.
1818 #---------------------------------------------------------------------------
1820 #---------------------------------------------------------------------------
1829 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1838 # man pages. In case the manual section does not start with a number, the number
1847 # will generate one additional man file for each entity documented in the real
1855 #---------------------------------------------------------------------------
1857 #---------------------------------------------------------------------------
1866 # relative path is entered the value of OUTPUT_DIRECTORY will be put in front of
1886 # listings (including syntax highlighting and cross-referencing information) to
1894 #---------------------------------------------------------------------------
1896 #---------------------------------------------------------------------------
1905 # If a relative path is entered the value of OUTPUT_DIRECTORY will be put in
1912 #---------------------------------------------------------------------------
1914 #---------------------------------------------------------------------------
1924 #---------------------------------------------------------------------------
1926 #---------------------------------------------------------------------------
1954 # The names of the make variables in the generated doxyrules.make file are
1955 # prefixed with the string contained in PERLMOD_MAKEVAR_PREFIX. This is useful
1962 #---------------------------------------------------------------------------
1964 #---------------------------------------------------------------------------
1967 # C-preprocessor directives found in the sources and include files.
1973 # in the source code. If set to NO only conditional compilation will be
1974 # performed. Macro expansion can be done in a controlled way by setting
1989 # If the SEARCH_INCLUDES tag is set to YES the includes files in the
2005 # patterns (like *.h and *.hpp) to filter out the header-files in the
2013 # defined before the preprocessor is started (similar to the -D option of e.g.
2024 # macro definition that is found in the sources will be used. Use the PREDEFINED
2026 # definition found in the source code.
2032 # remove all references to function-like macros that are alone on a line, have an
2034 # typically used for boiler-plate code, and will confuse the parser if not
2041 #---------------------------------------------------------------------------
2043 #---------------------------------------------------------------------------
2055 # the path). If a tag file is not located in the directory in which doxygen is
2066 # If the ALLEXTERNALS tag is set to YES all external class will be listed in the
2072 # If the EXTERNAL_GROUPS tag is set to YES all external groups will be listed in
2079 # If the EXTERNAL_PAGES tag is set to YES all external pages will be listed in
2092 #---------------------------------------------------------------------------
2094 #---------------------------------------------------------------------------
2097 # (in HTML and LaTeX) for classes with base or super classes. Setting the tag to
2107 # http://www.mcternan.me.uk/mscgen/)) to produce the chart and insert it in the
2109 # the mscgen tool resides. If left empty the tool is assumed to be found in the
2114 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2115 # then run dia to produce the diagram and insert it in the documentation. The
2117 # If left empty dia is assumed to be found in the default search path.
2130 # Bell Labs. The other options in this section have no effect if this option is
2137 # to run in parallel. When set to 0 doxygen will base this on the number of
2138 # processors available in the system. You can set it explicitly to a value
2148 # sure dot is able to find the font, which can be done by putting it in a
2156 # The DOT_FONTSIZE tag can be used to set the size (in points) of the font of
2195 # collaboration diagrams in a style similar to the OMG's Unified Modeling
2245 # So in most cases it will be better to enable call graphs for selected
2256 # So in most cases it will be better to enable caller graphs for selected
2271 # dependencies a directory has on other directories in a graphical way. The
2273 # files in the directories.
2281 # Note: If you choose svg you need to set HTML_FILE_EXTENSION to xhtml in order
2282 # to make the SVG files visible in IE 9+ (other browsers do not have this
2295 # Note: For IE 9+ you need to set HTML_FILE_EXTENSION to xhtml in order to make
2303 # found. If left blank, it is assumed the dot tool can be found in the path.
2309 # contain dot files that are included in the documentation (see the \dotfile
2316 # contain msc files that are included in the documentation (see the \mscfile
2322 # contain dia files that are included in the documentation (see the \diafile
2328 # that will be shown in the graph. If the number of nodes in a graph becomes
2331 # children of the root node in a graph is already larger than
2356 # badly anti-aliased labels on the edges of a graph (i.e. they become hard to
2364 # files in one run (i.e. multiple -o and -T options on the command line). This
2373 # explaining the meaning of the various boxes and arrows in the dot generated