Update documentation for 7.2.0

This commit is contained in:
vsr 2013-04-17 15:23:36 +00:00
parent a94dbd7745
commit 9351fe0dfa
3 changed files with 14 additions and 14 deletions

View File

@ -2,8 +2,8 @@
\page bounding_box_page Bounding Box
Shows the dimensions of the bounding box for the selected
geometrical object. Creates corresponding shape (box) on "Apply".
Displays the bounding box dimensions for the selected
geometrical object and creates the corresponding box shape on "Apply".
\image html measures5.png
@ -16,7 +16,7 @@ a satisfactory performance.
\n <b>TUI Commands:</b> <em>[Xmin,Xmax, Ymin,Ymax, Zmin,Zmax] = geompy.BoundingBox(Shape)</em>,
<em>BBox = geompy.MakeBoundingBox(Shape)</em>, where \em Shape
is the shape for which a bounding box is computed.
is the shape for which the bounding box is computed.
See also a \ref tui_bounding_box_page "TUI example".

View File

@ -70,9 +70,9 @@ closed edge.</li>
<li> If <b>Reorder vertices taking into account distances</b> is
checked, the interpolation algorithm does not follow the order of
vertices but searches for the closest vertex.</li>
<li><b>Tangents</b> are two vectors, defining direction of curve at
its ends. Both or none vectors must be set. This option available only
if two above check boxes are not checked.
<li><b>Tangents</b> are two vectors, defining the direction at the ends of the
curve. It is necessary to set both vectors or none. This option is available only
if both above check boxes are not checked.
</li>
</ul>

View File

@ -2,15 +2,15 @@
\page geompy_migration_page Modifying Geometry Python scripts from SALOME 6 and before
\n With SALOME 7.2, the Python interface for Geometry has been slightly modified to offer new functionality:
\n In SALOME 7.2, the Python interface for Geometry has been slightly modified to offer new functionality:
<ul>
<li>\subpage tui_execution_distribution_page</li>
<li>\subpage tui_auto_completion_documentation_page</li>
</ul>
\n Scripts generated for SALOME 6 and older versions must be adapted to work in SALOME 7.2 with all functionality.
\n A compatibility mode allows old scripts to work in almost all cases, but with a warning.
\n Scripts generated for SALOME 6 and older versions must be adapted to work in SALOME 7.2 with full functionality.
\n The compatibility mode allows old scripts to work in almost all cases, but with a warning.
<b>Salome initialisation must always be done as shown below</b>
\n (<em>salome_init()</em> can be invoked safely several times):
@ -20,12 +20,12 @@ salome.salome_init()
\endcode
<b>Geometry initialisation is modified.</b>
\n old mode:
\n the old mode:
\code
import geompy
geompy.init_geom(theStudy)
\endcode
new mode:
\n the new mode:
\code
import GEOM
from salome.geom import geomBuilder
@ -36,8 +36,8 @@ geompy = geomBuilder.New(salome.myStudy)
<b> Of course, <em>from geompy import *</em> is no more possible.</b>
\n You have to explicitely write <em>geompy.some_method()</em>.
\n <b>Some variables are no longer in namespace <em>geompy.GEOM</em> but in namespace <em>GEOM</em>.</b>
\n All the occurences of <em>geompy.GEOM.</em> can be replaced by <em>GEOM.</em>.
\n <b>Some variables have been transferred from the namespace <em>geompy.GEOM</em> to the namespace <em>GEOM</em>.</b>
\n All occurrences of <em>geompy.GEOM.</em> can be replaced by <em>GEOM.</em>.
\n For instance:
\code
param_polyline = geompy.MakeCurveParametric("t", "sin(t)", "cos(t)", 0., 100., 100, geompy.GEOM.Polyline, theNewMethod=True)