Pushed the fixes to git.
Here is python macro I've been using to test the trace state. I add this to
the macro toolbar so I can run it with one click. It does a trace state,
clears all the sources views, then executes the trace to restore your
state. This means you can click the button at any
This fix will be committed after the git transition. I also fixed another
bug about adding scalar bars to the correct view when a state has multiple
views. Also added a new test.
Pat
On Thu, Apr 15, 2010 at 7:33 PM, Eric E. Monson emon...@cs.duke.edu wrote:
Thanks a lot for looking into it
Hey all,
I haven't been using the python trace or state trace much lately, but I just
noticed a problem that shows up both on the Ubuntu 64-bit 3.8 RC1 binary and
CVS PV 3.9 on OS X, so it might be pretty general. If I do:
PointSource: 100 pts, rad 10
Glyph: Sphere (the rest default)
and do a
Hi Eric,
Yeah, this never worked (well it worked for a while due to a bug, but
stopped working when I fixed the bug) It affects filters that have
Input properties with ProxyListDomain. Stream tracer, probe location are
other examples I can find. Turns out it was an easy fix, I'll push the
Thanks a lot for looking into it and finding a fix so quickly, Pat!
I need to set up some offline animations for some of my users and it's so much
easier now that all the python trace stuff is in place -- trace it, add an
AnimateReader at the end and then all I have to worry about is data file
