On Wed, Dec 15, 2010 at 08:33:47PM +0000, Juha Jäykkä wrote:
> > variables. The 'pipeline' is living in a different namespace than the
> > interactive namespace.
> Ah. And it is completely inaccessible from the interactive namespace?
No, nothing is completely inaccessible.
> Your memory is correct: I do mlab.clf() and, as you must be aware, there is
> nothing in the pipeline after that; there is not even a figure.
If you don't have a figure anymore, you must be closing it on top of
that.
> Could the engine be the culprit?
Yes, absolutely: the default engine is an application-level global.
> Can it and whereever it comes from be removed somehow?
Yes, it seems possible to kill the engine. Mayavi should simply fall back
on its feets and recreate one when needed.
I would do something like:
from enthought.mayavi.tools.engine_manager import engine_manager
from enthought.mayavi.core.registry import registry
engine_manager.current_engine = None
registry.engines = {}
After clearing and closing the scene.
Gaël
------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
MayaVi-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mayavi-users
