-
Notifications
You must be signed in to change notification settings - Fork 381
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
Timer displays incorrect time during round transition #74
Comments
Quick Update: the long break one days the same thing but that one turns to -10:01 before setting itself to 15:00 |
Thanks for the detailed issue report @Aborres. I've seen this behavior, too, but haven't tackled it yet. Your documentation of it is helpful, though! Basically what you're seeing is the difference between the current round time (25) and the next round time (3), which is 22. Regarding the minimize-to-tray feature, this should happen without having to restart the application, so I think that's a bug. I'll create a separate issue for that based on your findings. |
No worries, I can't expect you to start debugging it if you can't see the issue for yourself :) I think I have found a good way to replicate this, If you click on the little arrow to advance the clock while the time is running, the next time to press play it will take the curr time in the clock - the time that had passed in the clock before the click on the arrow. For example: Running a 25:00 min long timer. |
This issue has been resolved with b7a2419 and is availble on Thanks again! |
Hey,
I have been testing the app today for the first time, and it is being great so far (thanks).
However I have noticed this:
Everytime you press play the timer resets to 22:01 before setting its correct time.
When starting a break it resets to -22:01 and then sets itself to whatever you have configured it to do.
These are the settings I am using:
Also, If you accept feedback, it seems like the minimize to tray only works if you restart the app, it would be nice if it were to tell you.
Thanks!
Edit: spelling
The text was updated successfully, but these errors were encountered: