incorrect handling of timings spanning midnight
If the timer is running at midnight but my computer is idle, and after midnight I click the "Move timer back" button, Timelime records an entry for the time before midnight (which it shouldn't) and then an entry starting at midnight of 5124095576030430 hours (which, in seconds, is the maximum value for a 64-bit unsigned int — 1.84467440737096e+19 — which is what's recorded in the database). I guess the real tragedy is that I don't bill by the hour.
-
timer1.png
6.54 KB
-
timer2.png
5.16 KB
-
timer3.png
10.8 KB
-
timer4.png
12.1 KB
timer1.png
timer2.png
timer3.png
timer4.png
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Niko on 04 Dec, 2013 09:29 AM
Hi Dan,
I'm very sorry for the inconvenience, this is clearly a bug. Thanks for finding it!
The app automatically stops the timer at midnight and starts it again to make sure that the work time is assigned to the correct dates. That's why there are two timings recorded. When the computer went idle before midnight and you click the "Move timer back" button after midnight, the start date of the recorded timing is after the end date of the timing, thus giving the wrong duration.
Can you delete the faulty timing(s) and add the time manually?
I will fix this bug in the next update.
Thanks a bunch,
Niko
2 Posted by Dan S. on 22 May, 2014 08:54 AM
I've actually seen this same problem a few more times recently — not under quite the same conditions, but still when moving the timer back after being idle (and possibly showing incorrect idle time?). I'm not sure of the exact steps to reproduce it, but I suspect it's related to my having the "New day starts at" setting set to 6 AM. I'll try to pay closer attention the next time it occurs, but I figured I'd mention it in case you had any ideas.
Support Staff 3 Posted by Niko on 22 May, 2014 12:44 PM
Thank you Dan for letting me know. I will investigate!
If that happens again, please report it...
4 Posted by Dan S. on 22 May, 2014 05:17 PM
OK, reproduced it again, twice. It's possible that, rather than being specific to "New day starts at" setting, it's specific to controlling the timer using screen sharing from another Mac. My idle timer is set to 5 minutes.
Here were the steps:
1) Put Computer A in sleep mode.
2) Connect from Computer B to Computer A via the built-in Screen Sharing program, waking it up, and start the timer.
3) Switch to another window on computer B.
4) After a few minutes, switch back to Screen Sharing and look at the idle timer popup. (It might take a few tries for this to pop up, but I don't think it's dependent on it actually being enough time based on the idle setting.) The popup showed an incorrect idle time — for example, 7 minutes, even though it'd only been 1 minute.
5) Click "Move timer back" on the idle popup.
The menu bar then shows 5124095576030430 of time again for the day. For the case above, the timing showed 12:43 PM - 12:36 PM. In the DB, the duration was -382, i.e. negative 6 minutes.
My best guess is that screen sharing doesn't properly register as non-idle time and that's messing things up. Anyway, hopefully you'll be able to reproduce it.
Support Staff 5 Posted by Niko on 22 May, 2014 06:01 PM
Thank you Dan, very interesting!
I'll try to reproduce it and let you know...
Support Staff 6 Posted by Niko on 22 May, 2014 06:37 PM
Oh, yes I just reproduced it!
Your guess is right; when using screen sharing the idle-time is not registered properly.
I will figure something out that will fix this...
Thank you very much for finding this bug!
Support Staff 7 Posted by Niko on 23 May, 2014 12:20 PM
I have fixed this bug described by Dan. The fix will be available with the next update...
8 Posted by Dan S. on 23 May, 2014 06:20 PM
Thanks!