-
Notifications
You must be signed in to change notification settings - Fork 1
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
Autosave peaks annotations and do not lose them (re-open) after browser or jvm crash / computer restart #42
Comments
I think we should focus on avoiding any crashes rather than making everything super-persistent. |
Focus is good, but peak annotating is manual time consuming operation, for better user experience we need autosave. E.g. we cannot avoid JVM crash or just computer power failure. |
Moreover, it's totally not obvious that the annotations are not saved to the exported session. We should warn the user about it at the very least. |
Maybe let’s implement session autosave and include annotated peaks into session? |
You mean, include the peaks themselves in the session? Potentially, there can be a lot of them. Our annotations are about 500 records long, as far as I remember. Also, I would suggest to ask the user on startup whether they want to load the previous autosaved session or to start from scratch. |
At the moment if browser crash peaks could be lost, let's save them to cache so as not to miss anything
The text was updated successfully, but these errors were encountered: