apo [Wed, 19 Sep 2007 08:19:55 +0000 (08:19 +0000)]
Fix for Bug NPAL16764 - EDF 553 VISU :
In Animation Bad range by default in Scalarmap
The bug is fixed by introduction a special TMinMaxController interface which can be applied to a VISU colored 3D presentations.
+ // PAL16857(SMESH not conform to the MED convention) ->
+ // 1D - always along X
+ // 2D - always in XOY plane
+ anIsDimPresent[iDim] = iDim < aMeshDimension;
apo [Wed, 6 Jun 2007 11:00:31 +0000 (11:00 +0000)]
To fix Bug IPAL16138
- IOLS. Impossible to show animation dumped by python in 3.2.6
(To fix the bug properly it was necessary to remove usage of "myType" parameter of VISU objects at all)
apo [Fri, 1 Jun 2007 13:05:20 +0000 (13:05 +0000)]
To clarify IDL.
1. It is forbiden to change input of Prs3d objects outside of "3D Cache System". So, corresponding functions are removed from IDL (but stays as it is in implementation)
2. "ScalaraMapOnDefomedShape" presentation was modified in the following way:
a) Method
void SetScalarField(in string theMeshName, in string theFieldName, in long theIteration, in Entity theEntity)
was changed to the
void SetScalarField(in Entity theEntity, in string theFieldName, in long theTimeStampNumber)
b) Method
string GetScalarCMeshName()
was removed at all
c) Method
Entity GetScalarEEntity()
was changed to the
Entity GetScalarEntity();
c) Method
long GetScalarLIteration();
was changed to the
long GetScalarTimeStampNumber();
d) Method
string GetScalarCFieldName();
was changed to the
string GetScalarFieldName();
apo [Fri, 1 Jun 2007 12:59:11 +0000 (12:59 +0000)]
To clarify IDL.
1. It is forbiden to change input of Prs3d objects outside of "3D Cache System". So, corresponding functions are removed from IDL (but stays as it is in implementation)
2. "ScalaraMapOnDefomedShape" presentation was modified in the following way:
a) Method
void SetScalarField(in string theMeshName, in string theFieldName, in long theIteration, in Entity theEntity)
was changed to the
void SetScalarField(in Entity theEntity, in string theFieldName, in long theTimeStampNumber)
b) Method
string GetScalarCMeshName()
was removed at all
c) Method
Entity GetScalarEEntity()
was changed to the
Entity GetScalarEntity();
c) Method
long GetScalarLIteration();
was changed to the
long GetScalarTimeStampNumber();
d) Method
string GetScalarCFieldName();
was changed to the
string GetScalarFieldName();
apo [Thu, 31 May 2007 11:57:57 +0000 (11:57 +0000)]
Fix for Bug IPAL16061
- IOLS. AttributeError on load script dumped from the attached study
To fix the bug the VISU IDL was changed.
TISOSURFACE enumeration item was changed to TISOSURFACES ("S" - was put on the back). It was done as from lexical, as from consistency with persistent mechanism point of views.
By the way, TPRSMERGER enumeration item was removed at all, because all functionality of this class was moved to ScalarMap and the item has no sense anymore.
This commit was generated by cvs2git to create branch 'BR_Dev_For_4_0'.
Sprout from V3_2_0_maintainance 2006-09-18 05:44:26 UTC enk <enk@opencascade.com> 'Fix for Bug IPAL12882'
Cherrypick from V3_2_0_maintainance 2006-06-08 09:43:23 UTC admin <salome-admin@opencascade.com> 'This commit was generated by cvs2git to create branch 'V3_2_0_maintainance'.':
doc/salome/tui/VISU/sources/bg_salome.gif
src/VISU_SWIG/batch_test_events.py
src/VISU_SWIG/test_events.py
apo [Tue, 5 Sep 2006 08:19:23 +0000 (08:19 +0000)]
To fix compilation bug in case of Mandriva64 usage.
The used "glXGetProcAddressARB" function is conditionally declared in the "GL/glx.h". So, to be sure that the function will be acessible in compile time it is necessary to define the "GLX_GLXEXT_LEGACY" preporcessor variable before including the "GL/glx.h" header file.
apo [Mon, 21 Aug 2006 14:40:06 +0000 (14:40 +0000)]
Fix for
Bug PAL13237 - CRASH after trying to select a cell for "Selection Info".
Bug PAL13239 - Numerations of elements(nodes) for the same mesh in Mesh and Post-Pro modules are different.
The two bugs are bound together.
The integrated fixes provide more correct definition of mapping between MED and VTK as for MED Families as for MED Entities itself.
In case of definition of MED Families mapping it was necessary to increase the VTK index when the Family contains from mesh elements of different geometric type.
And MED indexes should be taken from MED not from VISU CONVERTER internal numeration.