Rolling back changes (commented out the modifications) made 28.02.05. The fix is...

diff --git a/src/GraphExecutor/DataFlowExecutor_PyDynInvoke.cxx b/src/GraphExecutor/DataFlowExecutor_PyDynInvoke.cxx
index ee6ed2168a7c5e01e1b9dfd093e7bb369cd97c41..6dcdb436d6fe5a0ef1eeeafb9e652be9f24b3c02 100644 (file)
--- a/src/GraphExecutor/DataFlowExecutor_PyDynInvoke.cxx
+++ b/src/GraphExecutor/DataFlowExecutor_PyDynInvoke.cxx
@@ -158,7 +158,7 @@ PyObject * GraphExecutor::InNode::InitPyDynInvoke( char * PyFuncName ,
     
     thePyRunMethod = Automaton()->PyFunction( PyFuncName ) ;
     
-    thePyRunMethod = NULL; 
+    //thePyRunMethod = NULL; 
     // asv 28.02.05 : VERY BAD fix of the following problem: after change of a function, 
     // the changes are NOT taken into account by Automation - it returns PyObject of the OLD function.
     // so here we force re-automating the PyObject EVERY TIME, regardless if the function has changed or not.
@@ -167,6 +167,8 @@ PyObject * GraphExecutor::InNode::InitPyDynInvoke( char * PyFuncName ,
     // A better solution (to be implemented): store the PyObject NOT in Automation map, but in
     // InLine node itself!  And if the method is changed - remove the PyObject and force to regenerate it.
     // But this means that PyObject must be stored in Editor's data model.
+    // asv 01.03.05 : the fix is not needed, the described bug is not reproduced.  To investigate:
+    // WHERE PyObject is removed from Automation map on function change. 
     
     if ( (*aPythonFunction).length() ) {
       if ( thePyRunMethod == NULL ) {