[vtkusers] possible bug in vtkProgrammableSource

[Malcolm Drummond]

Thanks - SetWholeExtent fixes everything.

Malcolm

----- Original Message -----
From: Lorensen, William E (Research) <lorensen at crd.ge.com>
To: 'Malcolm Drummond' <malcolm at geovision.co.za>; vtkusers
<vtkusers at public.kitware.com>
Sent: Monday, April 15, 2002 4:26 PM
Subject: RE: [vtkusers] possible bug in vtkProgrammableSource


> Looks like the problem still exists in 4.0. I added a line:
>
>  $out SetWholeExtent 0 9 0 9 0 9
>
> to the proc and all works well. I suspect some changes in  the pipeline
update mechanism is causing
> it to fail without the SetWhOLEeXTENT.
>
> Bill
>
>
> -----Original Message-----
> From: Malcolm Drummond [mailto:malcolm at geovision.co.za]
> Sent: Sunday, April 14, 2002 4:41 PM
> To: vtkusers
> Subject: [vtkusers] possible bug in vtkProgrammableSource
>
>
> Hi
>
> I've found a problem with the programmable source object while upgrading
some scripts from 3.1 to 3.2
> (built from source downloaded around Jan 2002). It appears that the
StructuredPointsOutput is not
> being updated (perhaps only the polydata output works properly). The
attached script works fine under
> 3.1. Does anyone know anything about this bug? Maybe it's been fixed, but
I couldn't find anything in
> the archives.
>
> Also, I don't have 4.0 installed yet - if there aren't any regression
tests on the different output
> types could someone try this script.
>
> Malcolm
>
>
>