Comments on: JavaScript timeclocks

By: Sterling Camden

Sterling Camden — Fri, 30 Oct 2009 19:31:19 +0000

Corrected. I took the simpler approach of specifying the radix as the second argument to parseInt.

Sterling Camden — Fri, 30 Oct 2009 19:23:37 +0000

Oh, that’s bizarre. I’ll have to correct that. Thanks.

Etan Lightstone — Fri, 30 Oct 2009 19:11:33 +0000

Found the solution, it is related to a bug in javascript’s parseInt.

All you have to do is wrap parsefloat inside parseint. It is all explained here:

Short Answer:

ParseInt(“09″), returns 0

ParseInt(parseFloat(“09″)), returns 9

Etan — Fri, 30 Oct 2009 18:35:07 +0000

Hi Sterling,

There seems to be a pretty serious bug in how your stop watch interprets a time (manually typed or stopped), and then starts timing again.

Example: Stop the clock at 9 seconds, hit start again, it resets to zero.

Any idea why?

Thanks!

Sterling Camden — Wed, 17 Dec 2008 16:40:11 +0000

I came up with it for my own needs — tracking my consulting time. Nice blog you’ve got over there — subscribed.

Programming Tutorials — Wed, 17 Dec 2008 03:47:41 +0000

Ah seems like a great idea for an application. Did a client think of it or yourself? Good job!

Sterling Camden — Fri, 05 Dec 2008 01:07:55 +0000

You mean of the desktop version? Sorry, I have zero experience coding for X11.

But this JavaScript version should work fine in any browser that supports JavaScript (with JavaScript enabled).

Eastwood — Fri, 05 Dec 2008 00:48:59 +0000

What? You didn’t code a linux version?

Stopwatch application in C# -- Chip’s Tips for Developers — Mon, 10 Nov 2008 20:05:01 +0000

[...] 11/10/2008: Here’s the JavaScript version. Tags: .NET, C#, csstopwatch, threads, timers, [...]