[awesomelvin]

Huh that's weird. It actually shows the correct 336h for a few milliseconds first and then counts back from 35h. I wonder what's happening internally - messing up a timer shouldn't be that easy normally, right?

[mlyle]

Looks like losing the hundreds digit of hours-- truncation.

[dmonitor]

Because windows search is useless and if I search "timer" it'll probably bring up "timer.py" from a random application or just search bing