-
-
Notifications
You must be signed in to change notification settings - Fork 452
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
Scheduling of breaks - improved approach #1248
Comments
I think there maybe need to be more options for the suspend/lock situation:
I see the option at https://github.com/hovancik/stretchly#pause-breaks-on-suspendlock-, but it doesn't seem to include a reset option. |
there is no pause as you describe currently, everything is reset. |
Hrm. I guess there is a bug then? Because I have my minor breaks set to 15 mins and my major breaks set to 45mins, and I OFTEN see a minor break within a minute or two of opening my macbook lid after shutting it for a few minutes. |
Each OS works differently with closing lids, also this preference might change behavior https://github.com/hovancik/stretchly?tab=readme-ov-file#pause-breaks-on-suspendlock- . To be sure, check logs which should tell you what happens. |
OK, here is a weird example from the logs:
I don't understand how all those events are happening in between. I didn't touch the laptop at any of those times. I guess suspend on a macbook works differently to how I expected. |
It seems that when you were locking your laptop, Stretchly was paused already, this it did not pause for lock: |
OK, that makes some sense. It still seems like a bug, since obviously there is no benefit in resuming breaks while the laptop is asleep. Would make sense to prevent the resume until the laptop wakes. |
this comment will be updated with the latest thinking
Stretchly should update timers right away, when preferences are updated.
There should be option to remember current times passed when Stretchly is being paused/dnd/idle/sleep.
The text was updated successfully, but these errors were encountered: