I started using Ganib this week for a test if we will be able to deploy it to our team. The problem is that many tasks requires me to move around the company and g-track gets confused if I'm not typing and Rachota keeps complaining.
But after I spent 2 hours configuring another machine when I came back not even the screen that questions what I am doing appeared, it was completely frozen.
I killed the process, but when I start it again it says that it is already running or that it wasn't closed correctly, I reboot the machine and that message continued (but I was able to login and logout correctly correcting the problem.)
Now that I have successfully logged in with g-track there is a task that was added did came to g-track.
So my question(s) is(are), how stable is g-track? Should we get the team to update the information on the timesheet instead of g-track? Is there a way to make g-track consider at least 30 minutes before asking if the user is idle?