-
-
Notifications
You must be signed in to change notification settings - Fork 943
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
Stopwatch resets when leaving the app. #303
Comments
I think the problem is that the event which initializes the app is also called to reset the clock application after pressing the stop button. So that could be fixed by adding an additional method which gets invoked by the initialize event only if the state of the stopwatch is not set or if the stop button is pressed. Otherwise the old state is kept and the app just continues running with the last state. |
I got hit by this badly earlier. I started downloading the new LineageOS Nightly OTA to flash and then started a stopwatch. It notified me about the download being done a few seconds after the stopwatch had started which just cleared it. |
#783 implements persistence. |
Hello, |
You're right about it being related, #2141 should resolve this and is looking to be in really good shape to me |
Hello, I was using the stopwatch, and I noticed that whenever I closed the app, the stop watch would reset back to 0. Here is a video demonstrating the issue: https://www.youtube.com/watch?v=AcRQ5m9-PVQ
The expected behavior is having the stop watch still be running or atleast paused when the app is relaunched.
The text was updated successfully, but these errors were encountered: