From 53a2d715c239a6037af417fae71c1964d4b8aaea Mon Sep 17 00:00:00 2001 From: gdd Date: Fri, 2 Sep 2011 12:05:36 +0000 Subject: [PATCH] Doc of GHS3DPLUGIN (tui) --- .../gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc b/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc index 5d9dff78c..6623cb624 100644 --- a/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc +++ b/doc/salome/gui/SMESH/input/tui_defining_ghs3d_hypotheses.doc @@ -50,7 +50,9 @@ ghs3dMesh.Compute() # - a GEOM vertex or compound (No geometry, TUI only) # # The created enforced nodes can also be stored in -# a group (No geometry, TUI only). +# a group. +# +# This feature is available only on meshes without geometry. # Ex1: Add one enforced vertex with coordinates (50,50,100) # and physical size 2. @@ -120,7 +122,7 @@ GHS3D_Parameters.ClearEnforcedVertices() # It is possible to constrain GHS3D with another mesh or group. # The constraint can refer to the nodes, edges or faces. -# This feature is available only in TUI, on meshes without geometry. +# This feature is available only on meshes without geometry. # The constraining elements are called enforced elements for the mesh. # They can be recovered using groups if necessary. -- 2.39.2