public void SetCrossSectionMethod(
	PoMeshCrossSectionCrossSectionMethods method
)

Public Sub SetCrossSectionMethod ( 
	method As PoMeshCrossSectionCrossSectionMethods
)

public:
void SetCrossSectionMethod(
	PoMeshCrossSectionCrossSectionMethods method
)

member SetCrossSectionMethod : 
        method : PoMeshCrossSectionCrossSectionMethods -> unit 

Parameters

method

Type: OIV.MeshViz.DataPoMeshCrossSectionCrossSectionMethods

OIV.MeshViz.Data.PoMeshCrossSection.CrossSectionMethods.DEFAULT by default.

By default OIV.MeshViz.Data.PoMeshCrossSection builds a shape by computing an isosurface on a non regular mesh. The node's data are the distances to the plane. This method is safe but it uses a significant amount of memory for each instance of OIV.MeshViz.Data.PoMeshCrossSection.

Calling OIV.MeshViz.Data.PoMeshCrossSection.SetCrossSectionMethod(OIV.MeshViz.Data.PoMeshCrossSection.CrossSectionMethods)(OIV.MeshViz.Data.PoMeshCrossSection.CrossSectionMethods.INTERSECTION) forces the use of the classic method. The classic method computes the shapes by intersecting each cell with the plane. However it can be risky as it assumes that each mesh's cell is convex and therefore that the intersection of a plane and a cell's face can produce only one edge. Using the classic method with concave faces may produce unpredictable results or an infinite loop.

The environment variable OIV_3DDATA_CROSS_SECTION_METHOD can also be set to specify the method used to build this shape. It can take the values INTERSECTION or ISOSURFACE. However, calling OIV.MeshViz.Data.PoMeshCrossSection.SetCrossSectionMethod(OIV.MeshViz.Data.PoMeshCrossSection.CrossSectionMethods) overrides this environment variable.

Reference