[Paraview] Plugin works - doesnt - works - doesnt - ...

[Christian Werner]

Best thing is, when I just close the "odd" ParaView sessions right after 
startup (no image loading, nothing, just close), the filter always 
works. The plugin is loaded on startup though. When I disable autoload 
and load the filter on demand, then it again never works. It seems to 
get lost in ITK though, I have checked that now. The vtkImageData input 
that arrives at SimpleExecute is okay, but after converting back to VTK 
its gone...

But then again, in ParaView 3.6 and VTK-only it works perfectly.


Christian Werner wrote:
> Like this I always get the error message.
>
> This is what I wanted to say, the first time I start up ParaView 
> (after rebooting) always failed.
>
>
> Utkarsh Ayachit wrote:
>> If you start paraview with "-dr" command line option everytime, do you
>> still see the odd/even behavior?
>>
>> Utkarsh
>>
>> On Thu, Mar 18, 2010 at 2:20 PM, Christian Werner
>> <christian.werner at rwth-aachen.de> wrote:
>>  
>>> Hi!
>>>
>>> I am experiencing strange behaviour in ParaView. Believe it or not, 
>>> I have a
>>> plugin that works every second time I start Paraview. I am doing the 
>>> exactly
>>> same thing with one specific image, all steps are absolutely identical,
>>> still it works exactly only every second time.
>>> If I have, say, an even Paraview Session, the plugin works any time. 
>>> I can
>>> use it as much as I like, change values, update it, remove it, use 
>>> it again,
>>> ... it just works.
>>>
>>> The other (odd) time I get:
>>>
>>>
>>> Warning: In /opt/ParaView3.7/Servers/Filters/vtkTexturePainter.cxx, 
>>> line 180
>>>
>>> vtkTexturePainter (0x1b64340): Failed to locate selected scalars. 
>>> Will use
>>> image scalars by default.
>>>
>>>
>>> This holds for an older and the actual cvs version 3.7. When I 
>>> compile the
>>> plugin for 3.6 it works ALWAYS.
>>>
>>> I have difficulties in locating what the problem is. It seems that 
>>> it is
>>> because I am using ITK filters in this plugin (derived from
>>> vtkSimpleImageToImageFilter) - all my VTK-only filters work without a
>>> problem. Maybe these scalars get somehow messed up during the 
>>> conversion
>>> between ITK and VTK (every second time ...)
>>>
>>> I know this most probably won't help you developers find any bug but 
>>> I am
>>> asking because maybe this is somehow a known issue...? Something 
>>> must have
>>> changed since Paraview 3.6 here... Since it works for many image 
>>> types it is
>>> quite big, so I can't attach it to let you check this.
>>>
>>>
>>> Best regards,
>>> Christian
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
>>>     
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at: 
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview