This works (as I said above), but *NOT* to do that was exactly our proposal.
Using "send <in time>" takes only the CPU time the animation needs, the rest is taken by the system. Your variant, the "wait", stops for the whole time everything else: No watch is running, no other screen update, everything is blocked by doing "nothing" (while waiting).
For example see the difference by that:
Create a field, set locktext of it to true and set its script to the following (= a "Text-clock"):
Code: Select all
put not runShow into runShow
if runShow then
put the internet date into me
send "showTime" to me in (1000 - the millisecs mod 1000) millisecs
else put "Click me for a digital clock" into me
Then watch what this "Text-clock" does ...
(a) ... with your script: it stops until you click again (outside of its rectangle).
(b) ... with one of our scripts above: the clock goes on during the animation.
Our non-blocking scripts are proposals, nothing more.
p.s.Click the field only ONCE each time