[vtkusers] Memory usage and ReleaseDataFlag
Lisa S. Avila
lisa.avila at kitware.com
Thu May 31 11:03:52 EDT 2001
The ReleaseDataFlag is for the input, not the output of a filter. If you
have a filter A that provides output that is connected to multiple filters
B, C, and D, then you can have the ReleaseDataFlag on for filter A, but you
have to be careful with B, C, and D. The ReleaseDataFlag is most useful
when you know your pipeline will execute once (or quite infrequently at
least). In that case, you can manually call update on B and C, then have
the ReleaseDataFlag on for D and call update on that one last.
You should have no problem having the ReleaseDataFlag on for a filter
supplying data to a vtkTexture.
Of course, the above is "how it should work" and it is possible that you
have encountered a bug.
At 07:43 PM 5/30/2001, John Biddiscombe wrote:
>If a filter outputs a dataset and
>filter->SetReleaseDataFlag is true
>and the output is used as an input to multiple filters. Should the data
>only be released when all filters consuming the output have updated. I
>seem to be getting multiple updates and trouble.
>An image filter outputting an image which is passed into vtkTexture can't
>have ReleaseDataFlag(1) can it? Otherwise the texture reexecutes on every
>render. True or false (true from where I'm sitting, but I don't really
>believe it). Have I done something wrong.
>This is the private VTK discussion list. Please keep messages on-topic.
>Check the FAQ at: <http://public.kitware.com/cgi-bin/vtkfaq>
>Follow this link to subscribe/unsubscribe:
More information about the vtkusers