[cig-commits] commit: Adding this 'hardcoding' of the virtual function that sets the getMinGlobalFieldMagnitude & _getMaxGlobalFieldMagnitude. Previously these function were not being set and things were breaking for visualisation. I think it's safe to 'hardcore' this functionality at the ParticleFeVariable stage because I can't think of any child of ParticleFeVariable that would calculate it's min/max functions not using _FeVariable_GetMinGlobalFieldMagnitude or _FeVariable_GetMaxGlobalFieldMagnitude. If you think otherwise let me know.

[Mercurial]

changeset:   390:652b314deeb1
branch:      1.4.x
user:        JulianGiordani
date:        Tue Jan 19 15:07:09 2010 +1100
files:       MaterialPoints/src/ParticleFeVariable.c
description:
Adding this 'hardcoding' of the virtual function that sets the getMinGlobalFieldMagnitude & _getMaxGlobalFieldMagnitude. Previously these function were not being set and things were breaking for visualisation. I think it's safe to 'hardcore' this functionality at the ParticleFeVariable stage because I can't think of any child of ParticleFeVariable that would calculate it's min/max functions not using _FeVariable_GetMinGlobalFieldMagnitude or _FeVariable_GetMaxGlobalFieldMagnitude. If you think otherwise let me know.


diff -r 31eeedcc0483 -r 652b314deeb1 MaterialPoints/src/ParticleFeVariable.c
--- a/MaterialPoints/src/ParticleFeVariable.c	Thu Jan 14 17:40:48 2010 +1100
+++ b/MaterialPoints/src/ParticleFeVariable.c	Tue Jan 19 15:07:09 2010 +1100
@@ -70,6 +70,8 @@ ParticleFeVariable* _ParticleFeVariable_
 	   and so should be set to ZERO in any children of this class. */
 	nameAllocationType = NON_GLOBAL;
 	_syncShadowValues  = _FeVariable_SyncShadowValues;
+	_getMinGlobalFieldMagnitude = _FeVariable_GetMinGlobalFieldMagnitude;
+	_getMaxGlobalFieldMagnitude = _FeVariable_GetMaxGlobalFieldMagnitude;
 
 	self = (ParticleFeVariable*) _FeVariable_New(  FEVARIABLE_PASSARGS  );