Open Avispa opened 3 months ago
Thank you very much for opening up this issue! I am currently a bit overwhelmed by the many requests that arrive each week, so please forgive me, if I fail to respond personally. I am still very likely to at least skim read your request and I'll probably try to fix all (real) bugs if possible and I will likely review every single PR being made (please, give me a heads up if you intent to do so) and I will try to work on popular requests (please upvote via thumbs up on the original issue) whenever possible, but trying to respond to every single issue over the last years has been kind of draining and I need to adjust my approach for this project to remain fun for me and to make any progress with actually coding new stuff. Thanks for your understanding!
I agree that we should change this! Help with it would be very welcome!
This issue is still relevant. I opened my SupProd in the morning at 6 am, when I come back to the computer at 6pm, it said I'd worked for 12 hours continuously. This is ongoing for a few weeks already and still persist in the latest version of 10.0.1, and is annoying.
I adjusted the behavior to only count up the workedWithoutABreakTine
when tracking or when time is tracked via idle or the time tracking reminder. Not sure if this is ideal, but I think it is a good start for now.
System
Expected Behavior
Current Behavior
Steps to Reproduce (for bugs)
Break Reminder
enabled (which is be default).See also #3053: Overly agressive pomodoro timer.