> The dark side of this patch is that you are limited to one or two inputs
> portsit would be nice to have more flexibility. It would be nice to
> define the number of input ports directly in the XML plugin file.
Yes indeed. This was just a quick hack to demonstrate the
functionality with
Thanks Utkarsh!
It's a neat hack, and it will fit my problem perfectly.
The dark side of this patch is that you are limited to one or two inputs
ports. It would not be possible to create more complex filter like, for
example, the vtkLandmarkTransformFilter (which needs 3 separate input
ports).
> Elaborate. Why would changing names create backwards compatibility issues?
> You mean for Python scripts?
Yes, Python and XML state files will be affected. We can handle that,
but it's worth weighing the pros and cons for any such changes.
___
Elaborate. Why would changing names create backwards compatibility issues?
You mean for Python scripts?
From: Utkarsh Ayachit [mailto:utkarsh.ayac...@kitware.com]
Sent: Monday, July 18, 2016 7:48 AM
To: Scott, W Alan
Cc: paraview@paraview.org
Subject: [EXTERNAL] Re:
Dear all,
I have many LES results on a stationary mesh. Is it possible to store
mesh and time dependent flow fields in separate VTU files, so that I can
save some disk space.
Many thanks,
Feng Gao
___
Powered by www.kitware.com
Visit other Kitware
James,
Thanks for sharing your solution. That seems like a reasonable
approach to achieving what you need.
I was thinking you might be able to use the animation controls to
specify the centers of your sphere, but that does not appear to be
possible with discrete sphere positions. You can do some
The attached patch for vtkPythonProgrammableFilter along with a minor tweak
to your plugin XML does the trick. I can have this cleaned up and merged in
"master" for 5.2 if that's acceptable.
Utkarsh
On Fri, Jul 15, 2016 at 3:20 PM, Utkarsh Ayachit <
utkarsh.ayac...@kitware.com> wrote:
> Doh! I
I am going to say it's just historical. Maybe since filtering is an action,
"Transform" filter went with action verbs while since the Display
properties (on the Properties tab) are the state of the item, they went
with noun forms -- but that's just a guess.
While I have no objection changing one