Lines Matching refs:a
4 # doxygen (www.doxygen.org) for a project.
6 # All text after a hash (#) is considered a comment and will be ignored.
25 # The PROJECT_NAME tag is a single word (or a sequence of words surrounded
30 # The PROJECT_NUMBER tag can be used to enter a project or revision number.
36 …ide an optional one line description for a project that appears at the top of each page and should…
49 # If a relative path is entered, it will be relative to the location
57 # Enabling this option can be useful when feeding doxygen a huge amount of
84 # the brief description of a member or function before the detailed description.
90 # This tag implements a quasi-intelligent brief description abbreviator
98 # "represents" "a" "an" "the"
103 # Doxygen will generate a detailed section even if there is only a brief
109 # inherited members of a class in the documentation of that class as if those
122 # can be used to strip a user-defined part of the path. Stripping is
130 # The STRIP_FROM_INC_PATH tag can be used to strip a user-defined part of
131 # the path mentioned in the documentation of a class, which tells
132 # the reader which header file to include in order to use a class.
146 # will interpret the first line (until the first dot) of a JavaDoc-style
149 # (thus requiring an explicit @brief command for a brief description.)
154 # interpret the first line (until the first dot) of a Qt-style
157 # an explicit \brief command for a brief description.)
162 # treat a multi-line C++ special comment block (i.e. a block of //! or ///
163 # comments) as a brief description. This used to be the default behaviour.
164 # The new default is to treat a multi-line C++ comment block as a detailed
176 # a new page for each member. If set to NO, the documentation of a member will
181 # The TAB_SIZE tag can be used to set the number of spaces in a tab.
186 # This tag can be used to specify a number of aliases that acts
190 # will result in a user-defined paragraph with heading "Side Effects:".
222 # parses. With this tag you can assign which parser to use for a given extension.
223 # Doxygen has a built-in mapping, but you can override or extend it using this
224 # tag. The format is ext=language, where ext is a file extension, and language
234 # to include (a tag file for) the STL sources as input, then you should
254 # and setter methods for a property. Setting this option to YES (the default)
255 # will make doxygen replace the get and set methods by a property in the
257 # setting a simple type. If this is not the case, or you want to show the
265 # all members of a group must be documented explicitly.
270 # the same type (for instance a group of public functions) to be put as a
277 # When TYPEDEF_HIDES_STRUCT is enabled, a typedef of a struct, union, or enum
279 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
280 # with name TypeT. When disabled the typedef will appear as a member of a file,
291 # probably good enough. For larger projects a too small cache size can cause
293 # causing a significant performance penalty.
296 # a logarithmic scale so increasing the size by one will roughly double the
299 # corresponding to a cache size of 2^16 = 65536 symbols
314 # If the EXTRACT_PRIVATE tag is set to YES all private members of a class
319 # If the EXTRACT_STATIC tag is set to YES all static members of a file
338 # extracted and appear in the documentation as a namespace called
368 # documentation blocks found inside the body of a function.
375 # that is typed after a \internal command is included. If the tag is set
396 # will put a list of the files that are included by a file in the documentation
407 # If the INLINE_INFO tag is set to YES (the default) then a tag [inline]
452 …led and doxygen fails to do proper type resolution of all parameters of a function it will reject a
453 … the implementation of a member function even if there is only one candidate or it is obvious whic…
454 # will still accept a match between prototype and implementation in such cases.
488 # the initial value of a variable or macro consists of for it to appear in
490 # here it will be hidden. Use a value of 0 to hide initializers completely.
522 # The FILE_VERSION_FILTER tag can be used to specify a program or script that
532 # The LAYOUT_FILE tag can be used to specify a layout file which will be parsed
536 # You can optionally specify a file name after the option, if omitted
564 # parameters in a documented function, or documenting parameters that
586 # The WARN_LOGFILE tag can be used to specify a file to which warning
628 # excluded from the INPUT source files. This way you can easily exclude a
629 # subdirectory from a directory tree whose root is specified with the INPUT tag.
634 # directories that are symbolic links (a Unix file system feature) are excluded
649 # output. The symbol name can be a fully qualified name, a word, or if the
650 # wildcard * is used, a substring. Examples: ANamespace, AClass,
681 # The INPUT_FILTER tag can be used to specify a program that doxygen should
692 # The FILTER_PATTERNS tag can be used to specify filters on a per file pattern
695 # filter if there is a match.
696 # The filters are a list of the form:
711 # and it is also possible to disable source filtering for a specific pattern
712 # using *.ext= (so without naming a filter). This option only has effect when
721 # If the SOURCE_BROWSER tag is set to YES then a list of source files will
768 # will generate a verbatim copy of the header file for each class for
779 # contains a lot of classes, structs, unions or interfaces.
785 # in which this list will be split (can be a number in the range [1..20])
789 # In case all classes in a project start with a common prefix, all
806 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
817 # The HTML_HEADER tag can be used to specify a personal HTML header for
818 # each generated HTML page. If it is left blank doxygen will generate a
823 # The HTML_FOOTER tag can be used to specify a personal HTML footer for
824 # each generated HTML page. If it is left blank doxygen will generate a
829 # The HTML_STYLESHEET tag can be used to specify a user-defined cascading
832 # will generate a default style sheet. Note that doxygen will try to copy
840 # according to this color. Hue is specified as an angle on a colorwheel,
849 # the colors in the HTML output. For a value of 0 the output will use
858 # so 80 represents a gamma of 0.8, The value 220 represents a gamma of 2.2,
871 # NO a bullet list will be used.
877 # page has loaded. For this to work a browser that supports
886 # To create a documentation set, doxygen will generate a Makefile in the
898 # documentation sets from a single provider (such as a company or product suite)
903 # When GENERATE_DOCSET tag is set to YES, this tag specifies a string that
904 # should uniquely identify the documentation set bundle. This should be a
910 # When GENERATE_PUBLISHER_ID tag specifies a string that should uniquely identify
911 # the documentation publisher. This should be a reverse domain-name style
922 # Microsoft HTML help workshop to generate a compiled HTML help file (.chm)
929 # can add a path in front of the file if the result should not be
942 # controls if a separate .chi index file is generated (YES) or that
954 # controls whether a binary table of contents is generated (YES) or a
966 # that can be used as input for Qt's qhelpgenerator to generate a
989 # If QHP_CUST_FILTER_NAME is set, it specifies the name of a custom filter to
997 # <a href="http://doc.trolltech.com/qthelpproject.html#custom-filters">
998 # Qt Help Project / Custom Filters</a>.
1005 # <a href="http://doc.trolltech.com/qthelpproject.html#filter-attributes">
1006 # Qt Help Project / Filter Attributes</a>.
1042 # Note that a value of 0 will completely suppress the enum values from appearing in the overview se…
1046 # The GENERATE_TREEVIEW tag is used to specify whether a tree-like index
1048 # If the tag value is set to YES, a side panel will be generated
1049 # containing a tree-like index structure (just like the one that
1050 # is generated for HTML Help). For this to work a browser that supports
1057 # and Class Hierarchy pages using a tree view instead of an ordered list.
1068 # links to external symbols imported via tag files in a separate window.
1074 # when you change the font size after a successful doxygen run you need
1102 # MathJax, but it is strongly recommended to install a local copy of MathJax
1107 # When the SEARCHENGINE tag is enabled doxygen will generate a search box
1111 # (GENERATE_DOCSET) there is already a search function so this one should
1113 # can be slow, then enabling SERVER_BASED_SEARCH may provide a better solution.
1118 # implemented using a PHP enabled web server instead of at the web client
1137 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1173 # The LATEX_HEADER tag can be used to specify a personal LaTeX header for
1175 # the first chapter. If it is left blank doxygen will generate a
1183 # This makes the output suitable for online browsing using a pdf viewer.
1188 # plain latex in the generated Makefile. Set this option to YES to get a
1224 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1245 # config file, i.e. a series of assignments. You only have to provide
1265 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1294 # If a relative path is entered the value of OUTPUT_DIRECTORY will be
1300 # which can be used by a validating XML parser to check the
1306 # which can be used by a validating XML parser to check the
1335 # generate a Perl module file that captures the structure of
1349 # nicely formatted so it can be parsed by a human reader.
1377 # compilation will be performed. Macro expansion can be done in a controlled
1389 # in the INCLUDE_PATH (see below) will be search if a #include is found.
1408 # gcc). The argument of the tag is a list of macros of the form: name
1410 # omitted =1 is assumed. To prevent a macro definition from being
1417 # this tag can be used to specify a list of macro names that should be expanded.
1419 # Use the PREDEFINED tag if you want to use a different macro definition that overrules the definit…
1425 # that are alone on a line, have an all uppercase name, and do not end with a
1436 # can be added for each tagfile. The format of a tag file without
1444 # URLs. If a location is present for each tag, the installdox tool
1446 # Note that each tag file must have a unique name
1448 # If a tag file is not located in the directory in which doxygen
1453 # When a file name is specified after GENERATE_TAGFILE, doxygen will create
1454 # a tag file that is based on the input files it reads.
1480 # generate a inheritance diagram (in HTML, RTF and LaTeX) for classes with base
1498 # or is not a class.
1503 # available from the path. This tool is part of Graphviz, a graph visualization
1512 # explicitly to a value larger than 0 to get control over the balance
1517 # By default doxygen will write a font called Helvetica to the output
1519 # When you want a differently looking font you can specify the font name
1521 # which can be done by putting it in a standard location or by setting the
1533 # FreeSans.ttf font (which doxygen will put there itself). If you specify a
1540 # will generate a graph for each documented class showing the direct and
1547 # will generate a graph for each documented class showing the direct and
1554 # will generate a graph for groups, showing the direct groups dependencies
1559 # collaboration diagrams in a style similar to the OMG's Unified Modeling
1570 # tags are set to YES then doxygen will generate a graph for each documented
1577 # HAVE_DOT tags are set to YES then doxygen will generate a graph for each
1584 # doxygen will generate a call dependency graph for every global function
1586 # the time of a run. So in most cases it will be better to enable call graphs
1592 # doxygen will generate a caller dependency graph for every global function
1594 # the time of a run. So in most cases it will be better to enable caller
1600 # will generate a graphical hierarchy of all classes instead of a textual one.
1605 # then doxygen will show the dependencies a directory has on other directories
1606 # in a graphical way. The dependency relations are determined by the #include
1635 # nodes that will be shown in the graph. If the number of nodes in a graph
1637 # visualized by representing a node as a red box. Note that doxygen if the
1638 # number of direct children of the root node in a graph is already larger than
1640 # that the size of a graph can be further restricted by MAX_DOT_GRAPH_DEPTH.
1646 # from the root by following a path via at most 3 edges will be shown. Nodes
1649 # code bases. Also note that the size of a graph can be further restricted by
1650 # DOT_GRAPH_MAX_NODES. Using a depth of 0 means no depth restriction.
1654 # Set the DOT_TRANSPARENT tag to YES to generate images with a transparent
1658 # a graph (i.e. they become hard to read).
1670 # generate a legend page explaining the meaning of the various boxes and