Hi Seriema,
Glad to hear you like it!
Your suggestion of adding the option "count idle time as project time" to projects sounds very usefull, so I I'll add it. That would mean if a project that has this option checked is active, and the user becomes idle, the program will keep counting time towards that project instead of starting to count idle time. Do we agree? :-)
Right now WorkCoach starts counting idle time after one minute of user inactivity. I plan to make this time user configurable, so that might also help a little bit towards your problem.
I agree that it's inconvenient that you have to switch between the Project and Rules tabs, and that these two had better be combined or integrated somehow. I did it this way because I was afraid to make the GUI too complicated. You're suggestion to put the Add/Modify/Remove buttons under the Projects list in the Rules tab sounds like the best option right now. If you have any other ideas on this, let me know.
With regard to resetting the timer: the timer is now reset every day. The idea is that the program records the time spent on each project per day. I plan to save the project log to XML files (see my previous post) so you will have an XML file for each day containing time spent per project. Since they are XML files you can make HTML or even PDF reports (or other formats) from them with XSLT or XSL-FO. I might add a report function to the program later that can call these transformations.
I just noticed WorkCoach prioritizes projects without a window title rule over projects with one. Example, I had 2 projects:
Working in Visual Studio (a default rule)
My specific Visual Studio project (a rule for "devenv" with my title)
While working on my project, it counts towards the "Working in Visual Studio" project instead of my specific one. If I remove "Working in Visual Studio" then the time goes correctly to "My specific Visual Studio project". It should be the other way around..?
-Seriema
If you have a project containing a "wildcard rule", i.e. the window title rule is empty, that project overrules another project containing a rule for the same application, but
only if that other project is lower in the list than the project with the wildcard rule. (In other words: WorkCoach cycles through the projects and rules, starting at the top, and just takes the first one that matches.)
This is a known issue and described in the first post of this thread. I will definitely fix this since this is not desirable behaviour.
A workaround now is to make sure that the project with the wildcard rule is lower in the list than the project with the specific rule. Since you can't move projects up and down in the list, you'll have to do this by deleting and adding the project. We apologize for the inconvenience. :-)
Thanks for your feedback, and I'd be happy to hear about your further experiences.
Arjen.