A better system for autosaving the .mem files
Often, I will have made new cards in Mnemosyne but I forget to save them and my system crashes or whatever and I need to re-etnter all these cards. This can be very frustrating, especially since nearly all my other applications frequently autosave and I never have to worry about saving something.
The current scheme for autosaving I think is when you close the program? I think a better system would be for the program to autosave every so often, especially since I can't imagine the resource demands to be very high. What do people think?
Blueprint information
- Status:
- Started
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Peter Bienstman
- Definition:
- Approved
- Series goal:
- None
- Implementation:
- Beta Available
- Milestone target:
- None
- Started by
- Peter Bienstman
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Strange, because there is autosaving with each new card you add (not yet after each revision, for that we need the SQL backend first)
Andrew Lu: Is it maybe because the new cards were created by importing? I'm using 1.1.1 btw.
PB: yes, that'll be it
Work Items
Dependency tree
* Blueprints in grey have been implemented.