AutoHotkey Community

[lazygeek]

I'm spending way too much time on the computer.

Up to now, I was using a freeware app called TimeTracker to keep track of the total time I spend working on the computer per day. However it has a few nasty bugs and doesn't keep an accurate count under some circumstances. As it seems to be no longer developed, I tried looking for other free lightweight alternatives but couldn't find any, so I decided to quickly put something together using ahk.

Here you go. It's extremely simple (I'm new to the world of AHK) but i hope it can still be useful to some.

How to use it: there is nothing to configure, just launch it (best to have it
run at logon) and it will start tracking active usage time, based on mouse and keyboard input (the A_TIMEIDLE variable). Just hold down the right ctrl key to view the current usage for the day. The accuracy is +/-3 minutes.

For past data, you can check the track.txt file.

[Robbo]

I'm still trying it out but I like this script, nice and easy and I think quite useful! Good one!
_________________
All scripts are untested unless otherwise mentioned.

[lazygeek]

Robbo, glad you like it.

The script should be quite stable,
but if you encounter any bugs, please report.

Thanks for your feedback

[OceanMachine]

Thanks, very useful.

I changed

[OceanMachine]

I just added the ability to track idle time as well as active time, and also to log the total time (although this is obvious as it's just a sum of the two other numbers).

Hope you dont mind.

Not sure if anyone would find this useful, but thought I would post it anyway:

[Drugwash]

Case 1: machine runs more than 24 hours in a session
Case 2: script is (accidentally) closed and rerun or machine rebooted multiple times

What will this script display in any of the above situations?

Suggestions:
1. include a "session" section to count total active/idle time during current session
2. include a "today" section to count active/idle time for the current day, regardless of interruptions
3. modify the script to run in Win9x too (icon number may need to be changed too for 9x):

[OceanMachine]

The ini file is used to track the times, and is updated as soon as the 1 minute timer is fired. So yes, if the script is closed or rerun on a machine, it won't matter. the most you would be out by in any 1 counter would be 1 minute.

Regarding your points 1-3:

1: If the machine runs for more than 24 hours in one session, the times will still be posted as the date on which the script was run in that session, so if you opened the script on 3rd march and left it on for 30 hours, the total time would show for 30 hours on 3rd march (this is because the thedate variable is defined when the script is loaded). So, there shouldn't be a need for a session timer as this already works if you dont replace or close the script in the session (after midnight on the following day at least).

2: Assuming you want 1: to be obeyed as well, then this would need extra counters in there to count for the day and the session separately.

3: The only thing making it different on win9x is the icon and the hotkey, right? Well these can easily be changed, it doesn't have to be exactly the same on all OSs Maybe it would be possible to use the built in variables A_OSType and/or A_OSVersion to detect this and set things accordingly?

To stop the script being accidentally rerun while it is already running, you can add the following in the script (I usually put these at the top):

[lazygeek]

Glad to see this is generating some interest and nice suggestions .

I have amended the code in the original post with the 2 fixes suggested by OceanMachine. Thanks for this.

However, I will probably not be able to further update this script in the near future.

[Drugwash]

Hey OceanMachine, thanks for the details. Also thanks lazygeek for the initial script (should've said that in first post ).
Icon and hotkey apart, what I had in mind was basically a day counter for the current session. Something like:

Current session: 3 days 14 hours 25 minutes
Today's active: 4 hours 52 minutes
Today's idle: 0 hours 22 minutes

What I find odd is that the script has recorded 0 idle minutes, both yesterday and today (using OceanMachine's script version). I even lowered the idle check interval to 10,000 (10 sec) to no avail; there may be something wrong with that function under Win9x.

There's no yellow star in 98SE, not in shell32.dll at least. I'd settle for icon 25 instead, which is a file with an hourglass at the bottom-left. Or we could use one of the icons at famfamfam.com.

[OceanMachine]

Bear in mind that if you alter the timer value (from 60000) then you will also need to change the time interval check in the sub that is called by the timer. Additionally, changing this will mean that (for example) every 10 seconds your 'minute' counter would increase by one, so you would need to add some maths in there to only increment the minutes count if you were idle 6 times (if you had 10 seconds for the check frequency).

This made me notice that in my post with the idle timer modifications, I firstly didnt have A_TimeIdlePhysical in there (as per my original post in this thread - oops!), and secondly that the check is for 180000ms, not 60000ms as it should be for 1 minute.

@LazyGeek: you probably want to change

[Drugwash]

Yeah, figures. Also, it's funny that in a tool called AutoHotkey, hotkeys are the least usable (for 9x users), to begin with. Oh well...

Come to think about it, if the screensaver can detect activity, why the heck can't AHK do it too? Hmmm... food for thought (when my brains will stop boiling in own juice, that is).

See ya!

[OceanMachine]

[Drugwash]

I know but that'd be Chris' job not mine...

I'll take a look at Miranda's idle detection routine... probably... someday.

[OceanMachine]

That's just plain lazy...

It's not Chris's job at all, he has provided the platform upon which you can do what you like... if you should chose to use it to detect idle time, you can. He has been kind enough to provide a built in way to find the idle time on semi-recent operating systems... however not for those that went out with the ark, probably due to differences in the OS. Therefore you will have to do it in the same way that might approach any other problem and wish to solve it with AHK, and for which there isn't a nice easy built in variable... code it yourself

The vast majority of times we develop code there isn't a built in variable that gives you exactly what you need (in any platform), so the usual way is to generate that data yourself, not to start saying it is the developers job to provide you with a built in variable!

Good luck anyway

[Drugwash]

My point of view is that as long as there is a built-in function, it should work on all Win versions. At least that would be the kindest way to do things.

I can understand when due to many missing functions or libraries, there can't be overall compatibility (say, multi-monitor support for Win95/NT).

I've been working on a few scripts - mostly for personal usage - and although I'm running 98SE and couldn't care less about Win2000+, I've done my best (nagging neighbors and friends) to test and fix any issues that may appear while running under those OS versions. A little help in return would be welcome, IMHO.

Now, let's drop this silly argue and try to be constructive. I've promised I'd look into those Miranda sources and will do it, just as soon as I feel better after this bad cold. And I apologyze if any of my statements above looks rude - it's most likely the effect of the illness and medicine; don't wanna offend anyone.