eap [Tue, 9 Dec 2008 12:42:47 +0000 (12:42 +0000)]
0019292: EDF 672 SMESH : extend Composite side discretisation to 2D
/*!
+ * \brief Fill map of node parameter on geometrical edge to node it-self
+ * \param theMesh - The mesh containing nodes
+ * \param theEdge - The geometrical edge of interest
+ * \param theNodes - The resulting map
+ * \param ignoreMediumNodes - to store medium nodes of quadratic elements or not
+ * \retval bool - false if not all parameters are OK
+ */
+ static bool GetSortedNodesOnEdge(const SMESHDS_Mesh* theMesh,
+ const TopoDS_Edge& theEdge,
+ const bool ignoreMediumNodes,
+ std::map< double, const SMDS_MeshNode* > & theNodes);
All related controls for font definition in SMESH and VISU modules have been updated in accordance with changes on GUI_SRC level.
QtxFontEdit class and related controls in preferences has been updated in order to support custom fonts instead of system fonts only. For example VTK viewer uses only three fonts Arial, Courier and Times. As result there is no point in providing control with system fonts for VTK viewer. Also "S" button has been added in QtxFontEdit in order to provide "Shadow" style of VTK font. "underline" property of QFont is replaced with "overline" property in order to store "Shadow" status of font to avoid conflict simultaneous usage of "U" and "S" button.
All related controls for font definition in SMESH and VISU modules have been updated in accordance in changes in QtxFontEdit and related preferences functionality.
QtxFontEdit class and related controls in preferences has been updated in order to support custom fonts instead of system fonts only. For example VTK viewer uses only three fonts Arial, Courier and Times. As result there is no point in providing control with system fonts for VTK viewer. Also ?S? button has been added in QtxFontEdit in order to provide ?Shadow? style of VTK font. ?1underline? property of QFont is replaced with ?overline? property in order to store ?Shadow? status of font to avoid conflict simultaneous usage of ?U? and ?S? button.
sln [Wed, 26 Nov 2008 15:29:10 +0000 (15:29 +0000)]
0019939: EDF 762 SMESH : Definition of groups from other existing groups
?Union of two groups?, ?Union of two groups? and ?Cut of two groups? dialog boxes are updated for supporting works with several groups instead of two groups only
New ?Create group of underlying entities? dialog box is provided. It is intended for creating groups of entities from existing groups of superior dimensions (groups of nodes from group of faces, for example). Dialog contains
1) line edit for defining name of new group,
2) combo-box for defining dimension of elements (nodes, edges, etc),
3) list-box for defining source groups
sln [Wed, 26 Nov 2008 15:28:12 +0000 (15:28 +0000)]
0019939: EDF 762 SMESH : Definition of groups from other existing groups
SMESH_Mesh.idl is extended with:
SMESH_Group UnionListOfGroups(in ListOfGroups aListOfGroups,
in string name );
SMESH_Group IntersectListOfGroups (in ListOfGroups aListOfGroups,
in string name);
SMESH_Group CutListOfGroups (in ListOfGroups aMainGroups,
in ListOfGroups aToolGroups,
in string name);
for supporting works with several groups and
SMESH_Group CreateDimGroup( in ListOfGroups aListOfGroups,
in ElementType anElemType,
in string name );
for creating groups of entities from existing groups of superior dimensions
Orientation of faces is added for new elements' preview (remark for issue 0017291: EDF 591 SMESH : Visualization of the orientation of the normal vector of the mesh faces)
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
Add new NETGEN parameters to Mesh_Triangle and Mesh_Tetrahedron algorithms
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
<message>
+ <source>SUBMESH_NOT_ALLOWED</source>
+ <translation>No sense in creating a submesh ignored by global algorithm "%1"</translation>
+ </message>
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
//================================================================================
/*!
+ * \brief Return name of the algorithm that does not support submeshes and makes
+ * submesh creation useless
+ * \retval char* - string is to be deleted!!!
+ */
+//================================================================================
+
+char* SMESHGUI_MeshOp::isSubmeshIgnored() const
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
+ bool IsSupportSubmeshes; //!< TRUE if the algo building all-dim elems supports submeshes
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
1) algo->Compute() depending on algo->SupportSubmeshes()
2)
+ /*!
+ * \brief Return true if no mesh entities is bound to the submesh
+ */
+ bool IsEmpty() const;
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
+ /*!
+ * \brief Return an alternative parameter for a node on seam
+ */
+ double GetOtherParam(const double param) const;
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
+ static SMESH_HypoPredicate* IsMoreLocalThan(const TopoDS_Shape& theShape);
[SALOME platform 0013410]: SubMesh not taken into account with Netgen 1D-2D et 1D-2D-3D
+ bool SupportSubmeshes() const { return _supportSubmeshes; }
+ // 5 - whether supports submeshes if !NeedDescretBoundary()