better error reporting

use lock count instead of message queuing to avoid py->py messaging deadlock
must clear Python error...

svn path=/trunk/; revision=2585

1 files changed, 3 insertions, 3 deletions

diff --git a/externals/grill/py/source/clmeth.cpp b/externals/grill/py/source/clmeth.cpp
index 92c6b4d3..489b7dc5 100644
--- a/externals/grill/py/source/clmeth.cpp
+++ b/externals/grill/py/source/clmeth.cpp
@@ -175,11 +175,11 @@ PyObject *pyext::pyext_outlet(PyObject *,PyObject *args)
 				// by using the queue there is no immediate call of the next object
 				// deadlock would occur if this was another py/pyext object!
 				if(lst->Count() && IsSymbol((*lst)[0]))
-					ext->ToQueueAnything(o-1,GetSymbol((*lst)[0]),lst->Count()-1,lst->Atoms()+1);
+					ext->ToOutAnything(o-1,GetSymbol((*lst)[0]),lst->Count()-1,lst->Atoms()+1);
 				else if(lst->Count() > 1)
-					ext->ToQueueList(o-1,*lst);
+					ext->ToOutList(o-1,*lst);
                 else
-                    ext->ToQueueAtom(o-1,*lst->Atoms());
+                    ext->ToOutAtom(o-1,*lst->Atoms());
 			}
 			else
 				post("pyext: outlet index out of range");