From 61b2416dce7a9d806427f28939e11d7f250265a6 Mon Sep 17 00:00:00 2001 From: ana Date: Fri, 13 Jan 2012 14:37:34 +0000 Subject: [PATCH] Fix for the bug IPAL22851: Sub-shapes spelling --- doc/salome/gui/SMESH/input/constructing_meshes.doc | 8 ++++---- .../gui/SMESH/input/tui_defining_blsurf_hypotheses.doc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/salome/gui/SMESH/input/constructing_meshes.doc b/doc/salome/gui/SMESH/input/constructing_meshes.doc index 5f7466998..fc818ab5b 100644 --- a/doc/salome/gui/SMESH/input/constructing_meshes.doc +++ b/doc/salome/gui/SMESH/input/constructing_meshes.doc @@ -132,7 +132,7 @@ failure is provided. \image html meshcomputationfail.png -After you select the error, Show Subshape button allows +After you select the error, Show Sub-shape button allows visualizing the geometrical entity that causes it. \image html failed_computation.png "Example of the invalid input mesh" @@ -144,7 +144,7 @@ computation reporting. There are the following possibilities: always show information box, only if an error occurs or never. By default, the information box is always shown after mesh computation operation. -Publish Subshape button publishes the subshape, whose meshing +Publish Sub-shape button publishes the sub-shape, whose meshing failed, in GEOM component as a child of the mesh geometry, which allows analyzing the problem geometry and creating a submesh on it in order to locally tune hypotheses. @@ -171,7 +171,7 @@ evaluation will be displayed in the following information box:
  • If the mesh contains concurrent submeshes, it is possible to change the priority of their computation, i.e. to change the priority of -applying algorithms to the shared subshapes of the Mesh shape.
    • +applying algorithms to the shared sub-shapes of the Mesh shape. To change submesh priority: @@ -205,7 +205,7 @@ is:
  • 2D Netgen 1D-2D with Hypothesis Netgen Simple parameters (Number of Segments = 12)
    • -The submeshes become concurrent if they share subshapes that can be meshed +The submeshes become concurrent if they share sub-shapes that can be meshed with different algorithms (or different hypothesises). In the example, we have three submeshes with concurrent algorithms, because they have different hypotheses. diff --git a/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc index 470d6c5fe..7ffb53e05 100644 --- a/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc +++ b/doc/salome/gui/SMESH/input/tui_defining_blsurf_hypotheses.doc @@ -14,7 +14,7 @@ import BLSURFPlugin box = geompy.MakeBoxDXDYDZ(200., 200., 200.) geompy.addToStudy(box, "box") -# get subshapes +# get sub-shapes Face_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["FACE"])[0] Edge_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["EDGE"])[0] Vertex_1 = geompy.SubShapeAllSorted(box, geompy.ShapeType["VERTEX"])[0] -- 2.39.2