[Paraview] problem with python script generated by trace for simple plot

[ali rostai]

Thanks,
Excuse me I forgot to add cc. Currently the performance is not such big
problem and this
was just a question in my mind.

Ali

On Sun, Oct 2, 2011 at 7:45 PM, pat marion <pat.marion at kitware.com> wrote:

> > Is it possible to disable showing the small window which shows the result
> of script?
>
> Unfortunatley, no.  Paraview can be compiled in a mode to do software
> rendering which does not require windows, but the paraview releases don't
> have this ability.  If you're concerned about speed, it would be more
> efficient if you modified the python script so that it looped over the files
> in the same run, instead of having to start up and shut down each time, and
> it could re-used the same window.
>
> Pat
>
> p.s. please remember to cc the mailing list so that everyone can have a
> chance to reply
>
>
> On Sun, Oct 2, 2011 at 8:13 PM, ali rostai <ali.rostai at gmail.com> wrote:
>
>> Hi Pat,
>>
>> This was exactly what trace generated. The only change I made in the
>> script was changing
>> of absolute paths to relative ones so that anyone can run the script....
>>
>> I moved the WriteImage() to the end and pvpython generates again the same
>> thing. Also when
>> I run script from gui I see the correct result in gui but the png file
>> this time is empty (just black view 660bytes files)
>>
>>
>> I was using Paraview 3.10.1 up to now and downloaded the paraview 3.12-RC
>> last night
>> and tried with that... Cool! pvpython seems to work and in the new
>> generated script I can
>> see that WriteImage() is at the end of file.
>>
>> And another Q that I have:
>> Is it possible to disable showing the small window which shows the result
>> of script?
>> It appears for a moment and then disappears. When running script on many
>> files it
>> makes the process much slower.
>>
>> Thanks a lot
>> Ali
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20111002/7a4bf5ca/attachment.htm>