0021406: EDF 1975 NETGENPLUGIN: Submesh hypothesis not taken into account
Correct the patch for
0021556: EDF 2222 SMESH: 3D mesh after projection impossible
- smWithAlgoSupportingSubmeshes[0].push_back( shDim2smIt->second );
+ smWithAlgoSupportingSubmeshes[3].push_back( shDim2smIt->second );
1) Don't clear selection at open of dialog;
2) Disable automatic insert of selected elements in the list box;
3) Don't clear mesh selection during geometry selection.
Apply all-dimensional algos ("algos1") before applying
non-all-dimensional algos which are more local than all-dimensional
algos of upper dimension than algos1.
E.g.
* global on a COMPOUND of SOLIDs: "Prism 3D"
* local on a SOLID: "Regular 1D"
* local on a FACE: "Projection 1D-2D"
Fix is to apply "Projection 1D-2D" before applying "Regular 1D".
In getMediumNodeOnComposedWire(), prevent an exception at setting a
medium node, already added to a sub-mesh in AddNode() due to
mySetElemOnShape==true, to another EDGE.
Fix for "LayerDistribution" hypothesis
+ * \brief Store a hypothesis wrapping this not published one.
+ *
+ * This hyp, which has no own parameters but is published, is used to store variables
+ * defining parameters of this hypothesis.
+ */
+ void SetHolderHypothesis(in SMESH::SMESH_Hypothesis hyp);
+ // a published hypothesis wrapping this not published one
+ SMESH::SMESH_Hypothesis_var myHolder;
Fix for "LayerDistribution" hypothesis
+ * \brief Store a hypothesis wrapping this not published one.
+ *
+ * This hyp, which has no own parameters but is published, is used to store variables
+ * defining parameters of this hypothesis.
+ */
+ void SetHolderHypothesis(in SMESH::SMESH_Hypothesis hyp);
Fix approach to storage of NoteBook variables.
Before the fix: names of variables are stored in PythonDump commands
and nothing is stored in the Study.
Problem: after variable removal, the PythonDump script becomes invalid.
Fix: names of variables are stored in the Study, PythonDump commands
store indices of variables within "StringAttribute".
class SMESH_Gen_i {
...
- void UpdateParameters(/*CORBA::Object_ptr theObject,*/ const char* theParameters);
+ void UpdateParameters(CORBA::Object_ptr theObject, const char* theParameters);
+ const std::vector< int >& GetLastParamIndices() const;
+ std::vector< std::string > GetAllParameters(const std::string& theObjectEntry) const;
Fix a problem with visualisation of 'left_translated' mesh.
SMDS_Mesh::SMDS_Mesh()
{ ...
- points->SetNumberOfPoints(SMDS_Mesh::chunkSize);
+ points->SetNumberOfPoints(0);
and 13_projection_3d.py scripts from CEA test base
fix the regression on test_Prism3D_Improved.py (imps9/K2)
+ // not add not quadrilateral FACE as we can't compute it
+ // else if ( !quadAlgo->CheckNbEdges( theMesh, face ))
+ // // not add not quadrilateral FACE as it can be a prism side
+ // // else if ( myHelper->Count( face, TopAbs_EDGE, /*ignoreSame=*/false ) != 4 )
+ // {
+ // notQuadFaces.push_back( face );
+ // }
and 13_projection_3d.py scripts from CEA test base
When projecting quadratic 1D mesh to a 'vertical' composite side, fix
node location before creating a quadratic segment in order to have a
valid position (U and shape) of medium node.
