500 ms to set a thumbpos??

J. Landman Gay jacque at hyperactivesw.com
Sun Apr 13 20:58:02 CEST 2014


On 4/13/14, 11:42 AM, Dr. Hawkins wrote:
> While looking for the holdup in some code,
>
>     put the milliseconds -strt into stp[4]
>     set the thumbpos of sb "dnaScroll" to chrPos
>     put the milliseconds -strt into stp[5]
>     ck "elapsed: " && stp[0] && stp[0] && stp[1] && stp[2] && stp[3] &&
> stp[4] &&stp[5]
>
> The output is
>      elapsed:  0 0 38 38 38 542 1026
>
> That's 500 ms, repeatable, for that single line of code setting a thumbpos.

The handler is counting cumulative milliseconds; step 5 is counting 
everything that executed in steps 1 through 5, including the logging 
statement. You'll get a more accurate time if you reinitialize strt to 
zero before setting each thumbpos.

-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com



More information about the use-livecode mailing list