Thanks very much Paul,
I must have had a senior moment, because I thought I had searched for 'createclock' and found nothing.
When I downloaded the example, it worked fine and was exactly what I had done in my test publication. I reduced my test publication to be identical to the example, but I still got the same error----but now the clock actually runs. The only difference between the two publications was the chapter window size?.....so I changed my one to match the example and the error disappeared?? I'm a bit baffled to say the least.......and I can't reproduce the original error on mine by reverting to the different window size. Very strange?
The point of this exercise was because I had noticed that the Clock Action has the option to display time down to hundredths of a second and I wondered if the Script Clock has the same capability....which it does
Code:
myClock = CreateClock("ScriptClock","clock_var","[hh],[mm],[ss],[ff]")
myClock.Start()
This will give you a script clock with hundredth of a second resolution BUT.....there is no 'myClock.GetTenths()' operation, however the tenths and hundredths can be extracted from the clock_var variable by using the following constant expressions in insert variable.
Code:
(clock_var.toString()).charAt(9)-------for tenths of a second
(clock_var.toString()).charAt(10)------for hundredths of a second.
so it is possible to have a script clock with resolution down to hundredths of a second. I haven't tested it's accuracy yet.
Login
FAQ
Search
