ATimeTracker
ATimeTracker copied to clipboard
Add minimum time threshold setting
In order to reduce accidental start/ stop, interrupted ranges and garbage intervals, why not add a minimal start-stop time, like 5 seconds, before a change is actually recorded? Then a user could fumble the start/stop and as long as the correction is made within 5 seconds, no problem. This doesn't have to affect the current behavior at all, and it's highly unlikely a < 5 second interval would be useful anyways.
This should be configurable in the settings, and a setting of 0 would give current (no threshold) behavior.
This is related to #40
Yes, this sounds a bit simpler then what is suggested in #40 .
the only non-simple part I can think of, is if you had a task "running" then clicked on other thing(s) (for durations < 5sec) and then clicked back on the running task, re-starting it, then it should end up "uninterrupted". knowwhatImean? as though you hadn't clicked elsewhere in the first place.