MeshViz Fixed Bugs

MeshViz 7.2

7.2 Final Release

• (#509) PoBaseView viewingEventCB callback was not implemented for Qt viewer.
  
  
• (#1795) PoMeshCrossSection did not support mixed data binding.
  
  
• (#2362) meshSkin rendering crashed when all cells were rejected from the filtering.
  
  
• (#2451) Crash occured when closing an IVF viewer that was displaying MeshViz nodes.
  
  

MeshViz 7.1

7.1.1 Patch : Bugs fixed as of June 28, 2008

• No change
  
  

7.1 Final release

• (#2272) MeshViz used too much memory to store unstructured 2D mesh, the connectivity property is not allocated unless it is used to save memory.
  
  
• (#2273) PoMeshFilled did not allow to disable Open Inventor normal generation when rendering a flat 2D unstructured mesh. This is now fixed with the new PoMeshFilled::useOverallNormal fields.
  
  
• (#2274) Wrong annotation values were displayed on isoValues depending on usage of digit integer format with exponential or not.
  
  

MeshViz 7.0

Patch 7.0.1: Bugs fixed as of February 20, 2008

• (#2152) PiMarchingCubeCase can't be included more than once by project.
  
  

7.0 Final release

• (#1444) Previously PoMeshCrossSection crashed if coloringType was set to COLOR_INHERITED and the dataset was not yet set up.
  
  
• (#1055) MeshViz crashed when one tried to increase the size of an existing mesh node.
  
  
• (#1480) MeshViz crashed using PbIndexedMesh3D and PoMeshSkin->setMesh, because of uninitialized internal pointer usage.
  
  
• (#1670) It was not possible to use an index > SHRT_MAX in the valuesIndex field of various MeshViz nodes derived from PoMesh.
  
  
• (#1974) The BoolVector class has been renamed SbBoolVector in order to avoid possible conflict with user applications.
  
  
• (#2049) The annotations of isovalues in range 10**-3 (or any range specified using the format 10**) weren't properly displayed.
  
  
• (#2089) PoMeshSkin crashed if the supplied mesh was empty.
  
  
• (#2111) MeshViz licensing with FLEXnet do not work.

MeshViz 6.1

Patch 6.1.2: Bugs fixed as of July 19, 2007

• (#1730) COLOR_TEXTURE_CONTOURING provided darker mesh representation than COLOR_CONTOURING.
  
  

Patch 6.1.1: Bugs fixed as of May 29, 2007

• (#1895) PoMeshSkin crashed when the associated mesh (PoMesh3D) was deleted then recreated. [P1]
  
  

6.1 Final release

• No change.

MeshViz 6.0

Patch 6.0.3: Bugs fixed as of December 4, 2006

• No change.
  
  

Patch 6.0.2: Bugs fixed as of November 27, 2006

• (#1497) PoMeshSkin didn't work when enabling a cell filter. This bug occurred only for gridded mesh (inherited from PbGrid3D). [P3]
  
  
• (#1649) [Windows] The debug MeshViz DLL did not generate debug error messages as expected. [P3]
  
  
• (#1651) When the PoDomain was modified in the X direction, the Y position of the linear axis title was too low. [P3]
  
  
• (#1676) PbMesh2D::getBoundingBox() returned invalid values. [P3]
  

Patch 6.0.1: Bugs fixed as of July 12, 2006

• (#1456) PoMeshCrossSection, PoMeshLevelSurf, and PoMeshSkin could be incorrectly updated when using transparency. When a transparency was added via a post rebuild callback or data mapping, the next rebuild of the PoMeshCrossSection/PoMeshLevelSurf was not correct and could crash. This occurred only if the transparencyValueDeletedParts was ≤1. [P1]
  
  
• (#1457) PoMeshSkin did't work correctly when using a cell filter with a data-per-vertex binding. [P1]
  
  
• (#1459) It should not have been possible to write out abstract class PoCellFilter into an .iv file, but it was. Reading such an .iv file crashed because the pure virtual method acceptCell couldn't be called. [P1]
  
  
• (#1485) Under some circumstances, PoMeshContouring crashed in PiContouring::addIsolineEdge. [P1]
  
  
• (#1498) The wrong first cross section was displayed when color contouring was enabled. [P1]

6.0 Final release

• (#1210) The data binding (PER_CELL or PER_NODE) specified in a PbMesh wasn't preserved when the mesh was set in a PoMesh object.
  
  
• (#1329) PoMesh3DVecCrossSection with PROJECTION_ON_NORMAL sometimes drew vectors parallel to the defined plane instead of perpendicular.
  
  
• (#1338) Isosurfaces (and cross sections) could have been incorrect on a wedge cell because the marching cube table was incorrect in one case of the 64 cases on a wedge cell.
  
  
• (#1370) Sometimes triangles were missing when displaying a cross section on PoIndexedMesh3D with OIV_3DDATA_USE_TRIANGLE_STRIP_SET set to 0.
  
  
• (#1393) Holes could appear when a cross section was exactly on the face of a cell.
  
  
• (#1408) PoMeshCrossSection did not display correctly when the data mapping contained data with transparency.

MeshViz 5.0

Patch 5.0.5: Bugs fixed as of October 17, 2005

• (#830) PoCurve3 crashed or the PoCurve3 geometry was not visible when the curveRep field was set to CURVE_SMOOTH. [P5]
  
  
• (#1170) findContainingCell sometimes failed to find the appropriate cell when working on a 2D mesh with 3D (x, y and z) coordinates. [P5]
  

Patch 5.0.4: Bugs fixed as of June 6, 2005

• (#1158) Any action on a scene containing a PoBase-derived node could cause a crash. When copying a scene containing a PoBase-derived node, the callback userData was set wrong in the copy. This caused a crash if the original copy had been deleted. [P4]
  
  
• (#1171) A new field, lowerUpperBoxes, was added to PoNonLinearValueLegend3 and PoLinearValueLegend.
  
  If TRUE, when N values are specified, N+1 boxes are displayed with interpolated colors. If FALSE, N-1 boxes are displayed.
  
  For compatibility with existing behavior, TRUE is the default.
  
  NOTE: Older versions of Open Inventor will not be able to read Inventor files that specify a value for this new field.
  
  [P4]
  
  

Patch 5.0.3: Bugs fixed as of March 11, 2005

• (#1015) SoNode::copy didn't keep the dataBinding of the source mesh. The data binding of the copied mesh was always PER_CELL. [P3]
  
  
• (#1067) PoMeshProbePoint didn't detect cells on a PoTriangleMesh2D mesh. [P3]
  
  
• (#1072) The destructor of PoMeshSkin crashed if a cell filter was enabled. [P3]
  
  
• (#1105) The mesh probe picked up the wrong elements on multiple parallel structures. This worked fine if all the elements were on the same plane. But if the FEM model had depth, the highlighted element no longer corresponded to the cursor position. [P3]
  
  

Patch 5.0.2: Bugs fixed as of December 10, 2004

• No change.
  
  

Patch 5.0.1: Bugs fixed as of October 8, 2004

• (#845) PoLogAxis crashed when the start and end values were between the same two consecutive integer values. [P1]
  
  
• (#872) PoCellFilter did not work correctly when the filter didn't accept the first cells of the mesh. [P1]
  
  

5.0 Final release

• (#54) The method PbTriangleMesh2D::getCell returned NULL on an existing cell if the Z values of the geometry were defined. (Same as eBUG #301).
  
  
• (#301) getCell for 3D triangle cell was not correct, and rtti info was not available. The PbIndexedMesh2D and PbTriangleMesh2D getCell and findContainingCell methods returned NULL when the mesh had a Z coordinate and when the cell that should be returned was a triangle.
  
  
• The PbCell class should also have rtti info available (needed for OivJava) or something like SoType. (Same as eBUG #54).
  
  
• (#332) The method PbMesh::getAdjacentCellsIndByFacet didn't work.
  
  
• (#498) Some iv files crashed when using the *_CONTOURING modes of the mesh skin representation.
  
  
• (#619) Missing cells. Some of the cells were not displayed in a section plane. However, if you moved the section position slightly, they were displayed.
  Not OK: position (0, 0, 0) normal (0, 1, 0). OK: position (0, 0.01, 0) normal (0, 1, 0).
  The mesh was tetra or hybrid (mixture of tetra and hexa) with layers.
  
  
• (#620) When you displayed a section of a specific model, control never returned from DATAVIZ400.dll. The mesh was tetra or hybrid (mixture of tetra and hexa) with layers.
  Not OK: section position (0, 0, 0) normal (0, 1, 0) OK: section position (0, 0.01, 0) normal (0, 1, 0)
  This was fixed by introducing a new method to compute a cross section (see method PoMeshCrossSection::setCrossSectionMethod). The default mode (ISOSURFACE) for such kind of a mesh solves the problem.
  
  
• (#689) The setValue method applied on the field PoParalCartesianGrid2D::mesh crashed.

DataViz 4.0

Patch 4.0.6: Bugs fixed as of January 20, 2003

• No change.

Patch 4.0.5: Bugs fixed as of November 10, 2003

• (#371) PoMeshCrossSection::rebuild method crashed when contouring and transparency were enabled and the cross section exited from the data. The crash occured in PoBase::deleteTransparencyParts (called by PoMeshCrossSection::rebuild). (This bug was previously reported fixed but it was not.) [P5]
  
  
• (#573) PoSceneView didn't clip 2D text. [P5]
  
  
• (#605) COLOR_TEXTURE_CONTOURING mode failed when the isolist didn't cover all the mesh values. (The display was correct in the other coloringType modes.) [P5]
  
  
• (#677) Under certain circumstances, DataViz crashed when you moved the cross section outside the data. (Duplicate of #371) [P5]
  

Patch 4.0.4: Bugs fixed as of September 19, 2003

• (#543) Time axes generated with PoTimeAxis sometimes showed incorrect time invervals ticked. [P4]

Bugs fixed in patches 1, 2, and 3

• (#500) A compilation error occurred when PoSceneView.h and SoQtExaminerViewer.h headers were declared in the same source file. The compilation gave the following error message:
  %OIVHOME%\include\DataViz/view/PoBaseView.h(159) : error C2061: syntax error : identifier 'XAnyEvent'
  
  
• (#507) The PoMeshLevelSurf destructor freed non-allocated memory.
  
  
• (#508) PoTimeAxis entered an infinite loop when time difference >= 12428 or < = 0.0001 days.
  
  
• (#552) The src\DataViz\Samples\view programs (view and sceneView) behaved strangely when the toggleCameraType button was used.
  
  
• (#553) SoWinViewer::toggleCameraType did not update the camera of the DataViz view.

OFFICIAL RELEASE: Bugs fixed as of March 27, 2003

• (#38) New 3D cell classes, PbWedgeCell and PbPyramidCell, were added to avoid certain crashes in PoMesh3DVecGridCrossSection.
  
  
• (#46) A PieChartRep node having to display more than 256 slices crashed.
  
  
• (#118) The PoPointsFieldBars class displayed bars having negative values incorrectly.
  
  
• (#139) When non-null offset and angle were set, the polar linear axis was positioned incorrectly.
  
  
• (#165) The header file PoDomainElement.h was missing from the DataViz distribution. The header files of all elements added by DataViz (and other extensions) need to be provided with the SDK because they are necessary for writing custom actions.
  
  
• (#173) PoMeshCrossSection now works correctly on 3D meshes with elements with non-planar faces.
  
  
• (#228) When applying an SoWriteAction to a scene with a PoPolarGrid2D property node, the action crashed if FOLD_NODE_WRITE_FORMAT was used in PoBase::setNodeWriteFormat.
  
  
• (#231) There was an infinite loop in the class PoStreamLineMotion (line + particle) when the start point of the streamline was outside the mesh.
  
  
• (#236) Previously it was necessary to explicitly include the DataViz lib in the linker command line because some pragma statements were missing from PoDataViz.h.
  
  
• (#278) autoCubeAxis didn't display the expected axis when the X, Y and Z axis had nonhomogeneous sizes. For example, an autoCubeAxis from (10., 0.01,0.1) to (50., 0.05,10.) didn't correctly display the axis and the faces of the cube.
  
  
• (#302) The cache never broken on mesh modification. So the display of mesh representations (such as PoMeshLine) wasn't updated after modification of the mesh geometry.
  
  
• (#303) There was a performance problem and excessive memory consumption using PoScatter or PoValuedMarkerField (seen when drawing 500,000 markers).
  
  
• (#337) Duplicate of #236.
  
  
• (#371) The PoMeshCrossSection::rebuild method crashed when contouring and transparency were enabled and the cross section exited from the data. The crash occurred in PoBase::deleteTransparencyParts (called by PoMeshCrossSection::rebuild).
  
  
• (#383) When isovalues were added dynamically to an existing scene, the PoMeshContouring node didn't display all the iso annotations included in the annotClippingPolygon. The meshContouring was correctly updated if annotClippingPolygon wasn't set.
  
  
• (#443) There was a crash in a contouring representation that was cured by turning off optimization of a specific method (PiContouringFilled::fillElemCutByIsoline).

DataViz 3.7

GraphMaster

• SoBoxHighlightRenderAction problems on scene including several PoSceneview. (#36)
  
  
• PoMultipleHistogram did not correctly draw in PERCENTAGE representation, the bars having value set to 0. (#48)
  
  
• Wrong display of PoItemLegend node when the titleString field was set to "" or " ". (#57)
  
  
• The pick action did not match the displayed scene including PoSceneView with ratio height/width different to 1. (#63)
  
  
• The method PoToVRML2Action::apply crashes on scene including DataViz nodes. (#116)

3D-MasterSuite 3.6.3

GraphMaster

• The PoCircleArcCtrRadTwoAngle with CENTER_CLOSE with an angle > 180 degree was drawn as it was with END_CLOSE. (TEBUG 0260007)
• The definition of an PoAutoCubeAxis node with one of the dimension set to 10E8 gave a wrong axis display. (TEBUG 0260008)
• The display of linear axis grid lines was wrong when axis defined on large data (for ex, 0. to 10E6). (TEBUG 0260014)
• SoBoxHighlightRenderAction with PoSceneView was not correct (TEBUG 0260015)

3DdataMaster

• method PbIndexedMesh3D::getCell did not return the right cell.
• method PbTetrahedronMesh3D::getCell returned a default unit cell if the tetrahedron included in the mesh was not correct (flat). Now the method returns a NULL pointer because a flat tetrahedron is not usable.

PlotMaster

• When texts was rendered with SoAnnoText3 and stroke fonts the output gave the same string with 2 different fonts. (TEBUG 0260046)
• SoImage node did not print correctly with SoCGMVectorAction. (TEBUG 0260029)

3D-MasterSuite 3.6

GraphMaster

• Circles primitives (PoCircle3CenterRadius,...) crashed on Windows if there were more than 3 circles.
• There was a problem of memory allocation using PbIsovaluesList with irregular isovalues list.
• PoPieChart2D/PoPieChart3D : the representation was incorrect if the pie chart has only one slice.
• The copy() method did not work with all 3D-MasterSuite nodes.
• The possibility to add a concatened string to legend values did not work properly.
• PoLinearAxis and PoPolarLinAxis did not take into account of the current PoNumericDisplayFormat.
• Correction of logarithmic axis when there is less than one graduation.
• There was a problem of bounding box computation with PoAutoCubeAxis if the grid lines was displayed.
• Axis crached if tickNumOrPeriod < 1 and tickSubDef = PERIOD_MAIN_TICK.
• maxValueSize field of PoLinearValueLegend and PoNonLinearValueLegend3 gave unpredicable results if it was not include in [0-1] interval.
• The reflect of the fields min and max of PoDomain was not correct when the setValue() method with SbVec2f parameters was called.

3DdataMaster

• Probes (PoMeshProbePoint) did not work with 2D triangular meshes and at the mesh limits of the 3D cartesian meshes.
• The reading of binary Inventor files containing meshes was impossible
• Mesh representations in contouring mode crashed with more than 200 isovalues.

PlotMaster

• SoVectorizeGDIAction did not work properly with scene graph containing SoImage nodes.

3DMasterSuite 3.5.2

GraphMaster

• Classes deriving from PoAxis did not rebuild correctly when the length of axis became null.
• Some nodes crashed in debug mode when they was deleted with Visual C++ 6.0.
• PoSceneView which did not display background.

3DdataMaster

• Some representation classes did not always take into account modifications of the data mapping and the isovalues.
• PoMeshSkeleton crashed with Visual C++ 6.0 if no data set is used.

PlotMaster

• SoVectorizeGDIAction did not work correctly when a HDC was used as argument of the output class SoGDIVectorOutput.
• There was a memory leak with the HLHSR_PAINTER mode.

3D-MasterSuite 3.5

GraphMaster

• PoAxis: the axes crashed if the number of graduations less than 2.
• PoNonLinearValueLegend3 : the color at the legend extremities were not always correct.
• PoLabelField : the numeric labels were incorrect if the  numeric display format was AUTO_FORMAT (see PbNumericDisplayFormat).
• PoAutoCubeAxis : neither axes nor graduations were visible if the cube was screen aligned.
• The automatic display format (see PbNumericDisplayFormat) looped forever in some particular cases. 

3DdataMaster

• The destructor of PoMesh3D could crash in some cases.
• When an instance of a derived class of PoMesh2D or PoMesh3D was deleted, the modification of the connected mesh (derived from PbMesh3D)could crash.
• PoMeshFilled::rebuild did not work when it was used with a mesh of type PbCartesianGrid2D if coloringType == COLOR_AVERAGE and if the dimensions (nx,ny)of the mesh were not equal.
• PoMesh2DVec, PoMesh3DVec could crash or loop forever if the field bodyLengthFactor was negative or nul.
• PbMesh::addValuesSet, PbMesh::addVecsSet did not work when addValuesSet (or addVecsSet) was used to modify a data-set already defined and if this data-set had an index > 0.
• PbMesh::getMinValuesSet, PbMesh::getMaxValuesSet, PbMesh::getMinVecsSet, PbMesh::getMaxVecsSet returned the wrong extrema when it was the last value of the set.
• (#92) Geometry of an existing PoRegularCartesianGrid2D node can't be changed if the new geometry is bigger than the old one.
• (#76) 3DMS crashed when all the mesh values are eliminated by the dataMapping.

PlotMaster

• SoVectorizePSAction : pattern size is now correct. It was relative to the nominal width.
• The rendering of a SoPointSet node was not correct if more than one color was defined in the diffuseColor of the current SoMaterial and if the current SoMaterialBinding was PER_VERTEX.
• Ratio problems are now fixed.