Lines Matching refs:description

53 # Using the PROJECT_BRIEF tag one can provide an optional one line description
55 # quick idea about the purpose of the project. Keep the description short.
126 # description of a member or function before the detailed description
134 # This tag implements a quasi-intelligent brief description abbreviator that is
136 # as the leading text of the brief description, will be stripped from the text
138 # text. Otherwise, the brief description is used as-is. If left blank, the
157 # description.
207 # description. If set to NO, the Javadoc-style will behave just like regular Qt-
209 # description.)
225 # line (until the first dot) of a Qt-style comment as the brief description. If
227 # requiring an explicit \brief command for a brief description.)
234 # a brief description. This used to be the default behavior. The new default is
235 # to treat a multi-line C++ comment block as a detailed description. Set this
1193 # brief description and links to the definition and documentation. Since this
1289 # default header when upgrading to a newer version of doxygen. For a description
1663 # project logo, title, and description. If either GENERATE_TREEVIEW or
1979 # description of the possible markers and block names see the documentation.