[Paraview] Strange things happening when executing a new filter

[Michael Jackson]

Executing twice is _not_ normal for a vtk pipeline. First thing to  
check is that during your RequestData(...) method you are not setting  
values of your class using a "Setter" method. This will cause your  
class to get marked as "modified" and the pipeline will run again.

There are also some interactions with "sub-pipelines" within your  
RequestData(...) method that can cause your filter to execute multiple  
times. Check for that also.

Mike


On Oct 6, 2008, at 8:22 AM, Natalie Happenhofer wrote:

> Hi!
> I´ve written a new filter for paraview and built it as a plugin.  
> This works fine, apart the fact that my filter does not work  
> correctly, i.e. paraview breaks down when I execute it.
> Well, I´ve started debugging it using a std::ofstream, which writes  
> some values of my filter in a logfile so I can check them for  
> correctness (i.e. did I get the correct point data, do I set the  
> output points correctly, etc. )
> Strangely, I noticed that paraview does not call my filter once, but  
> twice when I press the apply button. According to the logfile, the  
> first time my function is called, there are no problems, i.e. it  
> gets to the end and returns, later it is called again and does not  
> finish because an error occurs.
> I wanted to find out if this behaviour, that a filter´s Execute  
> function is called twice is normal, and let the vtkShrinkFilter  
> write something in my file when it is called. The vtkShrinkFilter is  
> just called once, as I would expect.
>
> Does anyone have an idea why my filter is called twice? If you need  
> more information, just tell me, I´m not sure how much or how little  
> to write so you can understand my problem..
>
> thx,
> NH
>
> Express yourself instantly with MSN Messenger! MSN Messenger  
> _______________________________________________
> ParaView mailing list
> ParaView at paraview.org
> http://www.paraview.org/mailman/listinfo/paraview