On 07/11/06, Prabhu Ramachandran <[EMAIL PROTECTED]> wrote: > >>>>> "Angus" == Angus McMorland <[EMAIL PROTECTED]> writes: > > >> Can you run any of the TVTK examples? cd to tvtk/examples and > >> run any of the examples you see there and see if those work. > > Angus> tiny_mesh, simple, array_animation, off_screen, & > Angus> texture_glyph all work as expected. Animated texture throws > Angus> an error that I suspect is unrelated: > > Angus> Traceback (most recent call last): File > Angus> "animated_texture.py", line 95, in ? img = > Angus> image_from_array(array_3d) File "animated_texture.py", line > Angus> 86, in image_from_array img.point_data.scalars = ary_2d > Angus> File "tvtk_classes/data_set_attributes.py", line 126, in > Angus> _set_scalars File > Angus> "/usr/local/scipy/enthought/src/lib/enthought/tvtk/tvtk_base.py", > Angus> line 400, in _wrap_call ret = vtk_method(*args) ValueError: > Angus> method requires a VTK object > > Are you using numpy? If so please try this: > > $ export NUMERIX=numpy > > and rerun the animated_texture.py and then try mayavi2 and any other > examples that used to fail.
Initially that made things worse, as I got an error along the lines of: This module was compiled with C-API 100002 whereas numpy was compiled with 100009. I've seen this before, so recompiled everything. I don't know what I need to do with enthought and an inplace build to remove previously compiled code cleanly (in numpy I delete the build directory between rebuilds), so I resorted to deleting and re-fetching the svn repository to refresh things. That fixed the compile version problem, and now animated_texture.py works okay, but the ivtk_example.py is still giving the same garbled window, and mayavi2 still displays only Set Envisage to use the workbench UI: True Set Envisage to use the workbench UI: True and then does nothing. There is a hint of an attempt to create a window after the second line is printed, but it's destroyed very quickly. > Angus> The ivtk_example doesn't work. It does display a window, a > Angus> screenshot of the top left-hand corner of which I've > Angus> attached. The rest of the window is a continuation of the > Angus> bottom-right edge. I also get the error: > > Angus> (python:5475): Gtk-CRITICAL **: gtk_widget_set_colormap: > Angus> assertion `!GTK_WIDGET_REALIZED (widget)' failed > > Angus> The window persists, with a working menu, but nothing > Angus> further happens until I Ctrl-C the process. > > This is very wierd. What happens if you resize the window? The shaded portion of the window resizes correctly, but doesn't affect the mess in the top-left hand corner. The menu works okay, and closes the window when file->exit is selected. The scrollbar in the top-left panel also responds normally, although nothing else moves on screen with it. > What is your setup? wxPython version? VTK version? $ dpkg -l \*vtk\* | grep ii ii libvtk5 5.0.1-4 Visualization Toolkit - A high level 3D visu ii libvtk5-dev 5.0.1-4 VTK header files for building C++ code ii python-vtk 5.0.1-4 Python bindings for VTK ii vtk-doc 5.0.1-4 VTK class reference documentation ii vtk-examples 5.0.1-4 C++, Tcl and Python example programs/scripts $ dpkg -l \*wx\* | grep ii ii libwxbase2.6-0 2.6.3.2.1.5 wxBase library (runtime) - non-GUI support c ii libwxbase2.6-dev 2.6.3.2.1.5 wxBase library (development) - non-GUI suppo ii libwxgtk2.6-0 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (GT ii libwxgtk2.6-dev 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (GT ii python-wxglade 0.4.1-2 GUI designer written in Python with wxPython ii python-wxgtk2.6 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (wx ii python-wxtools 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (wx ii python-wxversion 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (wx ii wx-common 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (co ii wx2.6-headers 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI toolkit (he I had some older versions of python-wxgtk and libwxgtk installed too, but I've just "apt-get --purge removed" them all and recompiled, and everything remains as advertised. $ dpkg -l swig | grep ii ii swig 1.3.29-2.1 Generate scripting interfaces to C/C++ code In [1]: numpy.version.version Out[1]: '1.0.1.dev3430' I'm under the impression all the post 1.0 numpys are roughly equivalent. Could this be my mistake? Doesn't really seem like that would explain this particular behaviour though. and in case it's relevant I'm also running ctypes 1.0.1 from sourceforge (not the debian testing version). > > Angus> I hope this sheds a little more light. I'm very happy to > Angus> run more tests if someone tells me what would be useful: > Angus> I'm afraid I've little idea where to start with this one. > > Thanks. BTW, you might also want to CC > [EMAIL PROTECTED] Done. > cheers, > prabhu Thanks for your help trying to sort this out. A. -- AJC McMorland, PhD Student Physiology, University of Auckland Secretary, Fencing North Inc. ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ MayaVi-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mayavi-users
