Skip to content
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

Bug fix: Resuming after *pause* #813

Closed
r3a1d3a1 opened this issue Dec 18, 2020 · 5 comments
Closed

Bug fix: Resuming after *pause* #813

r3a1d3a1 opened this issue Dec 18, 2020 · 5 comments

Comments

@r3a1d3a1
Copy link

Currently, pausing breaks resets all the timers and counters.
As one may expect from the word "Pause", it'd be better to keep them as they were after the pause period is over.

@armudgal
Copy link

Hey @hovancik. What is your take on this? If this is free to take, I would like to work on it. Said that, if you think I should start with some other issue please do let me know.
Thanks :D

@hovancik
Copy link
Owner

Hi @armudgal , this is free to take, but it requires some thinking. Stretchly does not have any "state" and I am pretty much sending a lot of events up and down. And it's all connected(with DND, idle time and such).

Here are some related cards: #503, #772

Feel free to take a look at the code and write here how would you solve it?

@nyx-haile
Copy link

Wouldn't it be better if you were prompted to take a break immediately after the pause? Or at least if the countdown continues running while paused but once it reaches zero it's paused there? I imagine that if you're using a productivity app and don't want to be interrupted and spend a significant amount of time using it, that after you're done would be a good time to take a break. In my use case (after zoom meetings) I'd like a break reminder then instead of 15 minutes later.

@hovancik
Copy link
Owner

Well, I guess depends how you use pause, whether it means you take your own break, or it's a time when you don't wanna be disturbed.

@hovancik
Copy link
Owner

hovancik commented Apr 2, 2023

closing in favor of #1248

@hovancik hovancik closed this as completed Apr 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants