Pixyco-XYZ/openmesh
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Added missing </li> tags.

Browse Source 
Turned STL awareness on.

git-svn-id: http://www.openmesh.org/svnrepo/OpenMesh/trunk@240 fdac6126-5c0c-442c-9429-916003d36597
This commit is contained in:
Mike Kremer
2009-11-23 13:27:08 +00:00
parent 366609767c
commit b97acacb9b
2 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
Doc/Doxyfile
View File

@@ -225,7 +225,7 @@ EXTENSION_MAPPING =
# func(std::string) {}). This also make the inheritance and collaboration # func(std::string) {}). This also make the inheritance and collaboration
# diagrams that involve STL classes more complete and accurate. # diagrams that involve STL classes more complete and accurate.
BUILTIN_STL_SUPPORT = NO BUILTIN_STL_SUPPORT = YES
# If you use Microsoft's C++/CLI language, you should set this option to YES to # If you use Microsoft's C++/CLI language, you should set this option to YES to
# enable parsing support. # enable parsing support.

16
Doc/mesh.docu
View File

@@ -67,18 +67,20 @@ The goals/features of the C++ implementation are:
<ul> <ul>
<li> Choose suitable types for scalars and coordinates (e.g. float, <li> Choose suitable types for scalars and coordinates (e.g. float,
double, exact arithmetic and two-, three-, or n-dimensional double, exact arithmetic and two-, three-, or n-dimensional
points). points).</li>
<li> Enhance each item type by your own attributes/properties, like <li> Enhance each item type by your own attributes/properties, like
e.g. adding a normal vector or a \c FaceHandle to class \c e.g. adding a normal vector or a \c FaceHandle to class \c
Vertex. Vertex.</li>
</ul> </ul>
</li>
<li> Efficiency: <li> Efficiency:
<ul> <ul>
<li> Avoid the overhead of virtual inheritance and virtual function calls. <li> Avoid the overhead of virtual inheritance and virtual function calls.</li>
<li> Resolve as many type/attribute dependencies as possible at <li> Resolve as many type/attribute dependencies as possible at
compile-time instead of testing for attributes at run-time compile-time instead of testing for attributes at run-time
(e.g. normal vectors for faces). (e.g. normal vectors for faces).</li>
</ul> </ul>
</li>
<li> Type-safety for handles, <b>no type-casting (*)</b>: Vertices, <li> Type-safety for handles, <b>no type-casting (*)</b>: Vertices,
(Half-)Edges, Faces know each other and their corresponding (Half-)Edges, Faces know each other and their corresponding
handles. handles.
@@ -89,7 +91,7 @@ The goals/features of the C++ implementation are:
Though under the hood void pointers are used, the casting is done Though under the hood void pointers are used, the casting is done
within the mesh, and the user transparently uses his handles as before.<br> within the mesh, and the user transparently uses his handles as before.<br>
As soon as the compiler adheres to the C++ standard the type-safe version As soon as the compiler adheres to the C++ standard the type-safe version
will be restored. will be restored.</li>
</ul> </ul>
*/ */
@@ -798,7 +800,9 @@ To make use of these constant circulators just add the prefix<br />
"Const" to the type specifier and add the prefix "c" to the function used to request "Const" to the type specifier and add the prefix "c" to the function used to request
the circulator of an item. Example:<br/> the circulator of an item. Example:<br/>
<code>ConstVertexVertexIter cvvit = mesh.cvv_iter(some_vertex_handle);</code> \code
ConstVertexVertexIter cvvit = mesh.cvv_iter(some_vertex_handle);
\endcode
The following code example now shows how to enumerate the 1-ring of each vertex: The following code example now shows how to enumerate the 1-ring of each vertex: