On Tue, Jan 21, 2014 at 8:17 PM, Martijn Coppoolse <
[email protected]> wrote:
> If you're changing that code anyway, could you please also take care of
> the following change:
> setTimeout("updateClock();",(60-d.getUTCSeconds())*1000);
> to
> setTimeout(updateClock,(60-d.getUTCSeconds())*1000);
>
> (i.e. pass the function itself to setTimeout, instead of passing a
> string to be evaluated).
>
Even better, since it's being run from inside updateClock():
setTimeout(arguments.callee, (60...))
:)
> Personally, I don't see the need for a clock on a web page, in general.
> Most screens have a clock in a corner somewhere anyway.
>
Amen!
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
