[vtkusers] Issues with large polydata datasets & capturing vt kOutputWindow data

[Wesley Brooks]

Thanks for the help!

I had a look for the vtkWin32ProcessOutputWindow but unfortunately
could not find it. It appears that it may not be wrapped for use with
python in the versions of vtk/python I have here. I had a further dig
around and found vtkFileOutputWindow which according to the included
documentation redirects the output to a file, from the error window.
One thing confuses me a little though, is this a global operation on
the imported vtk library? In other words do I need to tell the render
window directly what form of error output to use or just do somthing
similar to what follows at the beginning of my program (in python);

errOut = vtk.vtkFileOutputWindow()
errOut.SetFileName('VTKERROR.txt')
vtkStdErrOut = vtk.vtkOutputWindow()
vtkStdErrOut.SetInstance(errOut)

Thanks also for the tip about the flag in the boot.ini. I will try
this as soon as I have the above working but need to capture vtk error
messages better for error reports for the users to send to me.

Cheers,

Wes.

On 28/08/2007, Nithiananthan, Sajendra
<Sajendra.Nithiananthan at rmp.uhn.on.ca> wrote:
>
> > -----Original Message-----
> >
> > Dear Users,
> >
> > My application using python/vtk/wxPython is crashing and I'd
> > appreciate any advice to help track and fix the error.
>
> > Also when the software crashes the vtkOutputWindow pops up as a
> > separate window flashes past a load of messages and then goes white.
> > Is there any way to capture the output to this window so I can review
> > it's contents to help with the bug tracking? I'm using the
> > wxVTKRenderWindow.
> >
> > Thanks for any help,
> >
>
> You can try using vtkWin32ProcessOutputWindow so that the popup is in a
> different window which won't die when your program crashes.  Sample C++
> code:
>
>         vtkWin32ProcessOutputWindow *outputwin =
> vtkWin32ProcessOutputWindow::New();
>         vtkOutputWindow::SetInstance(outputwin);
>         outputwin->Delete();
>
>
> -SN
>
> This e-mail may contain confidential and/or privileged information for the sole use of the intended recipient. Any review or distribution by anyone other than the person for whom it was originally intended is strictly prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Opinions, conclusions or other information contained in this e-mail may not be that of the organization.
>