Commit 472f6c21 authored by David E. DeMarle's avatar David E. DeMarle

Use full precision instead of format strings for times

With corresponding change in the ParaView level caller, this eliminates
this Catalyst warning:
vtkPVTrivialProducer (0x51724d0): Requesting time 9.6 but only 9.6 is available

and the values in the parameter are now as exact as they can be
in text form. Note also that the filenames are changed in spec A
output. As I recall the formatting was done for the original javascript
viewer client which couldn't handle precise numbers or perhaps filenames.
No one is actively using or developing that project anymore so this
change is fine.
parent 1d760de4
......@@ -525,7 +525,7 @@ def make_cinema_store(proxies,
"color"+proxy_name, 'vis', [proxy_name])
fnp = ""
if forcetime:
if forcetime is not False:
# time specified, use it, being careful to append if already a list
tvalues.append(forcetime)
tprop = store.make_parameter('time', tvalues)
......@@ -689,7 +689,11 @@ def project_to_at(eye, fp, cr):
return at
def explore(cs, proxies, iSave=True, currentTime=None, userDefined={},
def explore(cs,
proxies,
iSave=True,
currentTime=None,
userDefined={},
specLevel="A",
camType='phi-theta',
tracking={},
......@@ -734,7 +738,7 @@ def explore(cs, proxies, iSave=True, currentTime=None, userDefined={},
ctime_float = None
if currentTime:
ctime_float = float(currentTime['time'])
ctime_float = currentTime['time']
# hide all annotations
view_proxy.OrientationAxesVisibility = 0
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment