Idle time not working after update to 1.3.8

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Upon starting timer, it seems idle time is not measured.
2. Restarting application does not fix the problem

After upgrading to 1.3.8 it no longer gives me a prompt regarding whether or 
not I want to count the idle time.  I've tried setting it to 5 minutes or 10 
minutes and it just does not work for me.

I'm using 1.3.8 and 10.5.8 on a Mac.

I suppose something running in the background COULD be affecting my 'idle' 
time, but I'm not using anything different than when I was running 1.3.7 or 
earlier versions.

Original issue reported on code.google.com by esbow...@gmail.com on 21 Aug 2010 at 7:04

[GoogleCodeExporter]

Check the settings. Maybe its turned off. 

Original comment by rbur...@gmail.com on 21 Aug 2010 at 11:09

[GoogleCodeExporter]

I thought that too, but the checkbox for Computer Sleep Detection IS checked, 
and the Idle Timeout is set to 300 seconds.

Could it be preferences?

Original comment by esbow...@gmail.com on 21 Aug 2010 at 11:12

[GoogleCodeExporter]

well if its turned on in prefs then it should work. Can you try and test with 
1.3.7 and/or previous versions and see with which version the problem started?

Original comment by rbur...@gmail.com on 22 Aug 2010 at 5:28

• Changed state: Reviewed

[GoogleCodeExporter]

Original comment by rbur...@gmail.com on 22 Aug 2010 at 5:28

• Added labels: Type-Defect

[GoogleCodeExporter]

Well I went back to 1.3.7 and the idle time was still not working.  Went back 
to 1.3.6 and it was not working.  Then noticed that it ERASED A BUNCH OF 
RECORDED TIME!!!

Great. I don't even care about the idle time not working now, but it would be 
huge if I could get back my time that is now missing.  I really wish there was 
a way to backup the recorded time before upgrading/downgrading.  This is the 
second time it's wiped out a bunch of my recorded time. 

Any suggestions? Is this feature already available and I'm a dumb ass for not 
knowing about it?

Original comment by esbow...@gmail.com on 22 Aug 2010 at 8:28

[GoogleCodeExporter]

Im sorry to hear that. Which version where you working with before you upgraded 
to 1.3.8?

The data is kept in ~/Library/Preferences/com.slooz.timetracker.plist  (if you 
have been using an older version like 1.2.6) or ~/Library/Application 
Support/TimeTracker/data.plist (for the 1.3.x series)

Original comment by rbur...@gmail.com on 22 Aug 2010 at 10:45

[GoogleCodeExporter]

Well to my knowledge it couldn't have been older than 1.3.6.  I just noticed 
since upgrading to 1.3.8 that the idle time detection stopped working.

I'm not 100% convinced it's an issue with Time Tracker though. My guess is that 
something on this machine is keeping it from being idle??? How does Time 
Tracker determine when it's idle? Mouse movement?

My only guess about the data missing is that by going to the 1.3.6 version it 
somehow deleted entries that were not 'tagged' as being created in the 1.3.6 
version? I have no idea how that works. 

Thanks for the path to the plist files. I found the one in Application support, 
but I'm still clueless why it removed the data. The strange thing is that it 
did not remove all the data, only some of it. Stuff I had from a few months ago 
is still there.

Original comment by esbow...@gmail.com on 22 Aug 2010 at 10:57

[GoogleCodeExporter]

@esbowman, what shall we do with this bug, did you try newer versions and do 
you still have the problem?

Original comment by rbur...@gmail.com on 19 Nov 2010 at 7:49

[GoogleCodeExporter]

So sorry for the late reply.  I honestly don't have a clue what happened, but I 
don't believe it's a problem with Time Tracker at all.  It's strange, but the 
moment I upgraded to Adobe CS5 the time tracker app started 'detecting' my idle 
time again.  I don't know if it's some background service that was keeping my 
cpu from idling?

Clueless.  It's working now though. The Adobe update "fix" could just be 
coincidence.  

Original comment by esbow...@gmail.com on 22 Nov 2010 at 8:33

[GoogleCodeExporter]

so I guess there is nothing wrong with TT. If you feel otherwise please reopen.

Original comment by rbur...@gmail.com on 11 Dec 2010 at 10:03

• Changed state: Invalid