Closed rommeswi closed 2 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 am actually a little bit confused because while the timer counts from the full pomodoro timer time, it seems that the next break is triggered according to the net time remaining. I will keep observing to check what's going on.
It was just working exactly as intended. Overall, it seems like the behavior is a bit inconsistent. I will reopen this if I find out more.
Problem Statement
Currently, if you assign untracked time to a task, a pomodoro session starts with the full timer remaining.
:grey_question: Possible Solution
I would expect that the pomodoro timer is set to the time remaining in the session if assigning to a task only. If the net time is negative, the timer should be set to 1 second (and thus immediately trigger a break). When assigning to "task and break", I would expect a full timer to run.
:arrow_heading_up: Describe alternatives you've considered
You could just leave it as it is but it is slightly unintuitive.