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

Samuel Crow samuel_crow_work at rocketmail.com
Tue Jul 15 17:28:26 EDT 2008


That wasn't it.  I was able to make an XCode project that would write to the current home address.  It wasn't a problem with the file permissions.

--- On Tue, 7/15/08, Samuel Crow <samuel_crow_work at rocketmail.com> wrote:

> From: Samuel Crow <samuel_crow_work at rocketmail.com>
> Subject: Re: [Paraview] What could cause a reader's code not to be accessed?
> To: "Robert Maynard" <robertjmaynard at gmail.com>
> Date: Tuesday, July 15, 2008, 8:47 PM
> Perhaps it has something to do with file permissions. 
> I'll check into it.
> 
> --- On Tue, 7/15/08, Robert Maynard
> <robertjmaynard at gmail.com> wrote:
> 
> > From: Robert Maynard <robertjmaynard at gmail.com>
> > Subject: Re: [Paraview] What could cause a
> reader's code not to be accessed?
> > To: samuel_crow_work at rocketmail.com
> > Cc: paraview at paraview.org
> > Date: Tuesday, July 15, 2008, 8:39 PM
> > given a correct path, it is working on my machine.
> (macbook
> > OSX10.4)
> > 
> > Samuel Crow wrote:
> > 
> >   I changed it to a full path and it still doesn't
> > generate a file.
> > 
> > 
> > --- On Tue, 7/15/08, Samuel Crow
> > <samuel_crow_work at rocketmail.com> wrote:
> > 
> >   
> >   
> >     From: Samuel Crow
> > <samuel_crow_work at rocketmail.com>
> > Subject: Re: [Paraview] What could cause a
> reader's
> > code not to be accessed?
> > To: "Robert Maynard"
> > <robertjmaynard at gmail.com>
> > Cc: paraview at paraview.org
> > Date: Tuesday, July 15, 2008, 8:15 PM
> > Thanks for the tip!
> > 
> > 
> > --- On Tue, 7/15/08, Robert Maynard
> > <robertjmaynard at gmail.com> wrote:
> > 
> >     
> >     
> >       From: Robert Maynard
> <robertjmaynard at gmail.com>
> > Subject: Re: [Paraview] What could cause a
> >       
> >     
> >     reader's code not to be accessed?
> >     
> >     
> >       To: "Samuel Crow"
> >       
> >     
> >     <samuel_crow_work at rocketmail.com>
> >     
> >     
> >       Cc: paraview at paraview.org
> > Date: Tuesday, July 15, 2008, 8:09 PM
> > The path you set "~/cubelog.txt" is an
> >       
> >     
> >     incorrect
> >     
> >     
> >       path, since the ~ is a 
> > terminal shortcut. Use a fully qualified path
> > 
> > Samuel Crow wrote:
> >       
> >       
> >         Here goes!
> > 
> > There's a bunch of stuff commented out. 
> >         
> >       
> >     
> >     Right now
> >     
> >     
> >       I'm just trying to display a white cube. 
> The
> > file
> > contents are ignored.
> >       
> >       
> >         
> > --- On Tue, 7/15/08, Robert Maynard
> >         
> >       
> >       <robertjmaynard at gmail.com> wrote:
> >       
> >       
> >           
> >         
> >         
> >           From: Robert Maynard
> >           
> >         
> >       
> >       <robertjmaynard at gmail.com>
> >       
> >       
> >         
> >           Subject: Re: [Paraview] What could cause a
> >           
> >         
> >       
> >       reader's code not to be accessed?
> >       
> >       
> >         
> >           To: samuel_crow_work at rocketmail.com
> > Cc: paraview at paraview.org
> > Date: Tuesday, July 15, 2008, 6:58 PM
> > Can you provide the source code, xml files
> >           
> >         
> >       
> >     
> >     and the
> >     
> >     
> >       
> >         
> >           CMakeList.txt?
> > 
> > Samuel Crow wrote:
> > 
> >   Correction:  The cube reader is based on
> > VTK/Examples/DataManipulation/Cxx/Cube.cxx
> >           
> >         
> >       
> >     
> >     not
> >     
> >     
> >       
> >         
> >           CubeSource.cxx
> > 
> > 
> > --- On Tue, 7/15/08, Samuel Crow
> > <samuel_crow_work at rocketmail.com>
> >           
> >         
> >       
> >     
> >     wrote:
> >     
> >     
> >       
> >         
> >             
> >   
> >     From: Samuel Crow
> > <samuel_crow_work at rocketmail.com>
> > Subject: [Paraview] What could cause a
> >           
> >         
> >       
> >       reader's code
> >       
> >       
> >         
> >           not to be accessed?
> > To: paraview at paraview.org
> > Date: Tuesday, July 15, 2008, 3:42 PM
> > 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
> > 
> > 
> >       
> > 
> > 
> >           
> >         
> >       
> >     
> >     _______________________________________________
> >     
> >     
> >       
> >         
> >           ParaView mailing list
> > ParaView at paraview.org
> > 
> >           
> >         
> >       
> >     
> >     http://www.paraview.org/mailman/listinfo/paraview
> >     
> >     
> >       
> >         
> >               
> >   
> >   
> > 
> >       
> > 
> > 
> >           
> >         
> >       
> >     
> >     _______________________________________________
> >     
> >     
> >       
> >         
> >           ParaView mailing list
> > ParaView at paraview.org
> > 
> >           
> >         
> >       
> >     
> >     http://www.paraview.org/mailman/listinfo/paraview
> >     
> >     
> >       
> >         
> >               
> >           
> >         
> >         
> > 
> >         
> >       
> >     
> >     
> >       
> > 
> > _______________________________________________
> > ParaView mailing list
> > ParaView at paraview.org
> > http://www.paraview.org/mailman/listinfo/paraview


      



More information about the ParaView mailing list