-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: Continuous timer feature with overtime logging #26
Comments
Hi @SZSage, Thank you for sharing the idea! However, this feature might conflict with the existing auto-start functionality. For instance, when the session ends, the timer might automatically switch mode and start a new cycle, this setup complicates the implementation of time extension. Additionally, I think this feature does not align with the Pomodoro technique advocated practice, which suggests using a complete Pomodoro as a basic unit to measure activities. let me know what you think, I am willing to hear more feedback before making this decision. |
Hi, this plugin is awesome :) I was very recently considering opening an issue to request a very similar feature. Thank you for continuing to improve this great plugin |
I think I need some more time to consider this feature. In case you weren't aware, you can disable the break mode by setting it to 0, and then enable auto-start. This way, the Pomodoro timer will continuously run in the work mode, this might also be a potential solution for this kind of use case. |
what about a bit more "manual flexibility"? i.e., making it possible to start new work cycle without having to do break, manually? for me, the tip about break = 0 is a good workaround, doing it now :) |
Hello, thank you for developing this awesome plugin!
I'd like to suggest a feature enhancement. It would be great if the timer could continue running beyond the set duration and log any additional time spent.
I believe this feature would add significant value for users who occasionally require extra minutes to wrap up their work.
Thanks!
The text was updated successfully, but these errors were encountered: