WORLD CRONOMETER UPDATE UPDATE

Looking at the dial, you can see the outermost city ring which stays in place. Not that a world time chronograph on a leather strap is what one imagines wearing while taking a swim, but still worth noting. What this crown isn’t going to help with is water resistance, which is 50m so this is definitely a watch you want to keep on dry land. Along with the stepped bezel, the crown adds some personality to the case. You’ll notice the pocket-watch style crown that looks somewhat like a desk-bell. It is not close to being a slim watch and on a smaller wrist, I can see it being a bit of a problem. The Ball Trainmaster Worldtime Chronograph comes in a 42mm wide polished steel case that sits at a hefty 13.7mm thick.

All things considered, the Ball Trainmaster Worldtime Chronograph offers a lot of impressive horological chops, handsome design, and good finishing for the money. That being said, Ball is likely aiming for a very specific buyer type who is likely a well-versed collector seeking a unique watch that pulls off being a subtle worldtimer chrono. The total package is a solid and handsome watch with a an impressive set of complications, albeit in a watch that can wear a little thick and oftentimes be devoid of some personality (though I’ve seen plenty of worldtimers with too much personality).

This is an updated version of the Trainmaster Worldtime Chronograph with mostly minor refinements. The Ball Trainmaster Worldtime Chronograph takes what could be a watch that’s bursting at the seams and through subtle design and color choices presents a timepiece that I preferred to wear as a dressier option that doesn’t have the bland personality or been-there-done that design of so many dressy chronographs out there. Their shock resistance, impressive lume, and association with the American railroad system has been the cornerstone of the brand’s identity, but I was not expecting to be as taken with a watch that features two complications that I rarely appreciate together, especially at a price point just over $4,000. makes some of the best under the radar and high-quality value proposition timepieces out there. And you'd probably want to add some kind of get/set function if you wanted to get the count or change the repeat value.It’s not news that Ball Watch Co. Comes in handy.Įdit: Note, this doesn't do any input checking (like if delay and repeat are the correct type. Self-corrects the setTimeout, can run it X number of times (-1 for infinite), can start running instantaneously, and has a counter if you ever need to see how many times the func() has been run. * Self-adjusting interval to account for drifting I've wrapped it up into a constructor function so we can do 'objecty' things with it. I'ma just build on Bergi's answer (specifically the second part) a little bit because I really liked the way it was done, but I want the option to stop the timer once it starts (like clearInterval() almost). SetTimeout(step, Math.max(0, interval - dt)) // take into account drift possibly special handling to avoid futile 'catch up' run Var dt = Date.now() - expected // the drift (positive for overshooting) Here the exact delay for each of the repeated timeouts is adapted to the actually elapsed time, compared to the expected intervals: var interval = 1000 // ms Those are known as self-adjusting timers. This requires a bit more advanced strategy (and code), though it pays out well (and registers less timeouts). However, sometimes you really need a steady interval executing your callbacks without drifting.

WORLD CRONOMETER UPDATE UPDATE

So it would be advisable to update more often, like about every 100ms, to avoid such jumps.

When the interval lags a bit and executes your callback after 990, 1993, 2996, 3999, 5002 milliseconds, you will see the second count 0, 1, 2, 3, 5 (!). Now, that has the problem of possibly jumping values. alternatively just show wall clock time: Output(Math.floor(delta / 1000)) // in seconds Var delta = Date.now() - start // milliseconds elapsed since start Then base your logic on the current time value, instead of counting how often your callback has been executed.įor a simple timer or clock, keep track of the time difference explicitly: var start = Date.now() Use the Date object instead to get the (millisecond-)accurate, current time.

They are allowed to lag arbitrarily, and they do not keep a constant pace but tend to drift (as you have observed). They cannot be trusted, there are no accuracy guarantees for them. Because you are using setTimeout() or setInterval().

World cronometer update