[Paraview] What could cause a reader's code not to be accessed?

[Samuel Crow]

Hello again,

My practice reader creates a file in its constructor and closes it in its destructor.  There is no file created when I put my "libCubeReaderGUIPlugin.dylib" and "libCubeReaderSMPlugin.dylib" into /usr/local/plugins/ , enter them into the plugin manager requester in the appropriate list gadgets, and try to open a *.cube file that I created.  The attempt at reading the file just produces 2 outputs with the first being a polygonal mesh with one point and no polygons in it, and the second being an unused uniform rectalinear grid.

The *.cube filetype is correctly registered by the client side so I know that the GUI plugin is working.  I'm using vtkPolyDataAlgorithm as my parent class in vtkCubeReader.h and am trying to follow the instructions in the VTK User's Guide and the ParaView Guide for making a reader.  The contents of my vtkCubeReader.cxx file is based on the VTK/Examples/Graphics/vtkCubeSource.cxx source code.  There is nothing proprietary in this reader yet so, if you need me to post code, I can post it to the list.

I'm running Paraview 3.2.2 on a Macintosh Pro with 4 GiB of RAM and 2 quad-core Xeon processors.

Thanks,

--Sam Crow