Lines Matching full:documentation
3 # This file describes the settings to be used by the documentation system
41 # project for which the documentation is generated. This name is used in the
48 # could be handy for archiving the generated documentation or if some version
60 # in the documentation. The maximum height of the logo should not exceed 55
67 # into which the generated documentation will be written. If a relative path is
104 # documentation generated by doxygen is written. Doxygen will use this
120 # documentation (similar to Javadoc). Set to NO to disable this.
153 # inherited members of a class in the documentation of that class as if those
180 # path mentioned in the documentation of a class, which tells the reader which
237 # documentation blocks is shown as doxygen documentation.
243 # documentation from any documented member that it re-implements.
249 # page for each member. If set to NO, the documentation of a member will be part
262 # the documentation. An alias has the form:
267 # documentation, which will result in a user-defined paragraph with heading
339 # documentation. See https://daringfireball.net/projects/markdown/ for details.
368 # classes, or namespaces to their corresponding documentation. Such a link can
401 # doxygen to replace the get and set methods by a property in the documentation.
409 # If member grouping is used in the documentation and the DISTRIBUTE_GROUP_DOC
410 # tag is set to YES then doxygen will reuse the documentation of the first
446 # the documentation of the scope in which they are defined (i.e. file,
447 # namespace, or group documentation), provided this scope is documented. If set
456 # typedef struct TypeS {} TypeT, will appear in the documentation as a struct
504 # documentation are documented, even if no documentation was available. Private
514 # be included in the documentation.
520 # methods of a class will be included in the documentation.
526 # scope will be included in the documentation.
532 # included in the documentation.
538 # locally in source files will be included in the documentation. If set to NO,
547 # included in the documentation. If set to NO, only methods in the interface are
554 # extracted and appear in the documentation as a namespace called
571 # members will be included in the various overviews, but no documentation
588 # documentation.
594 # documentation blocks found inside the body of a function. If set to NO, these
595 # blocks will be appended to the function's detailed documentation block.
600 # The INTERNAL_DOCS tag determines if documentation that is typed after a
601 # \internal command is included. If the tag is set to NO then the documentation
602 # will be excluded. Set it to YES to include the internal documentation.
625 # their full class and namespace scopes in the documentation. If set to YES, the
638 # If the SHOW_HEADERFILE tag is set to YES then the documentation for a class
645 # the files that are included by a file in the documentation of that file.
651 # grouped member an include statement to the documentation, telling the reader
658 # files with double quotes in the documentation rather than with sharp brackets.
664 # documentation for inline members.
670 # (detailed) documentation of file and class members alphabetically by member
685 # (brief and detailed) documentation of class members so that constructors and
689 # member documentation.
691 # detailed member documentation.
724 # list. This list is created by putting \todo commands in the documentation.
730 # list. This list is created by putting \test commands in the documentation.
736 # list. This list is created by putting \bug commands in the documentation.
743 # the documentation.
748 # The ENABLED_SECTIONS tag can be used to enable conditional documentation
756 # documentation. If the initializer consists of more lines than specified here
760 # documentation regardless of this setting.
766 # the bottom of the documentation of classes and structs. If set to YES, the
767 # list will mention the files that were used to generate the documentation.
792 # version. For an example see the documentation.
835 # Tip: Turn warnings on while writing the documentation.
848 # potential errors in the documentation, such as documenting some parameters in
856 # function parameter documentation. If set to NO, doxygen will accept that some
857 # parameters have no documentation without warning.
863 # are documented, but have no documentation for their parameters or return
865 # documentation, but not about the absence of documentation. If EXTRACT_ALL is
941 # documentation (see:
1059 # that contain images that are to be included in the documentation (see the
1148 # classes and enums directly into the documentation.
1175 # link to the documentation.
1182 # brief description and links to the definition and documentation. Since this
1319 # of the possible markers and block names see the documentation.
1359 # documentation.
1418 # documentation will contain a main index with vertical navigation menus that
1429 # documentation will contain sections that can be hidden and shown after the
1453 # create a documentation set, doxygen will generate a Makefile in the HTML
1456 # ~/Library/Developer/Shared/Documentation/DocSets so that Xcode will find it at
1464 # This tag determines the name of the docset feed. A documentation feed provides
1465 # an umbrella under which multiple documentation sets from a single provider
1472 # This tag determines the URL of the docset feed. A documentation feed provides
1473 # an umbrella under which multiple documentation sets from a single provider
1479 # This tag specifies a string that should uniquely identify the documentation
1488 # the documentation publisher. This should be a reverse domain-name style
1489 # string, e.g. com.mycompany.MyDocSet.documentation.
1495 # The DOCSET_PUBLISHER_NAME tag identifies the documentation publisher.
1516 # words in the documentation. The HTML workshop also contains a viewer for
1560 # the table of contents of the HTML help documentation and to the tree view.
1567 # generated documentation will be placed on the server by the user during the
1568 # deployment of the documentation. The generated sitemap is called sitemap.xml
1579 # (.qch) of the generated HTML documentation.
1654 # name. Each documentation set should have its own identifier.
1701 # doxygen will group on one line in the generated HTML documentation.
1743 # the HTML documentation. When you change the font size after a successful
1826 # example see the documentation.
1913 # to a relative location where the documentation can be found. The format is:
2009 # description of the possible markers and block names see the documentation.
2056 # files. Set this option to YES, to get a higher quality PDF documentation.
2207 # captures the structure of the code including all documentation.
2260 # the structure of the code including all documentation. Note that this feature
2271 # file that captures the structure of the code including all documentation.
2388 # file the location of the external documentation should be added. The format of
2394 # section "Linking to external documentation" for more information about the use
2404 # external documentation" for more information about the usage of tag files.
2473 # href=https://graphviz.org/doc/info/arrows.html>Complete documentation about
2642 # output formats in the documentation of the dot tool (Graphviz (see:
2674 # contain dot files that are included in the documentation (see the \dotfile
2680 # You can include diagrams made with dia in doxygen documentation. Doxygen will
2681 # then run dia to produce the diagram and insert it in the documentation. The
2688 # contain dia files that are included in the documentation (see the \diafile
2774 # contain msc files that are included in the documentation (see the \mscfile