My solution (not particularly eloquent) is to store the programmable filter in a file and read it into a string at the the beginning of the my script.
On Fri, Jan 23, 2009 at 6:33 PM, Pierre JUILLARD <pierre.juill...@gmail.com> wrote: > > Hi all, > > Can a python programmable filter be saved? > > As described on this wiki page, it is possible to export cutom programmable > filters (last part: "Managing custom filters"): > http://www.paraview.org/Wiki/Custom_Filters > > Is a similar mechanism available for python programmable filter? > It would be very interesting: > - having at hand, as soon as Paraview is started ones own usual scripts. > - having the possibility to execute them in a ParaView batch job (as I > understand it, once created, they are not currently saved with other > ParaView settings). > - easing the python programmable filter sharing between different paraview > installations. > > Please, could you indicate me if such a feature is available? > It doesn't appear so in: > http://www.paraview.org/Wiki/Python_Programmable_Filter > > I thank you in advance for your help. > > Cheers, > > Pierre > > _______________________________________________ > ParaView mailing list > ParaView@paraview.org > http://www.paraview.org/mailman/listinfo/paraview > > _______________________________________________ ParaView mailing list ParaView@paraview.org http://www.paraview.org/mailman/listinfo/paraview