-
Notifications
You must be signed in to change notification settings - Fork 277
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
make "save" the default behavior #1183
Comments
I just had exactly the same happen to me, what is the reason behind not autosaving? |
The data is there, go to History. You may need to recalculate in the menu. There is not much that can be done if the activity is killed, there is no "dafault" action. |
I lost data, it's not in the History tab. I think I clicked on stop without clicking on save, but retrying that and killing the app manually doesn't result in lost data as you say, so I'm not sure what happened. I'll come back on this if I manage to reproduce my issue. |
Nope, that's the first place I looked. I think the problem could also be fixed by removing the "back" arrow button in the top left, that's where I went wrong. |
Great app, thanks for making it!
I just tried the app and immediately lost my run. Needing to press the save button at the bottom means that unless you scan the entire UI, or if you make a single mistap, your whole run is gone. Which, believe me, is very frustrating.
Unless discard is pressed, the default behavior should be to save the run.
The text was updated successfully, but these errors were encountered: