keepass2android Preserve unsaved changes before locking the database.

Preserve unsaved changes before locking the database.

Open NumbGnat opened this issue 7 years ago • 5 comments

Could you add a save before locking? Many times I've been in the middle of adding an entry and I noticed my phone went into snooze before I saved. The entry was completely lost, although I had already set up the account with the web site, so I lost the password and had to use their recover feature.

You could use a specific icon or list them in italics at the top, with some indication that they were "recovered" or "unsaved". Perhaps use a custom folder named, "Recovered".

You could use a custom string on the saved entry to track the folder path and item name that the unsaved changes relate to.

Users could open the "recovered" entry and choose to apply or merge the changes.

Likewise, opening an existing entry that has a matching "recovered" entry would prompt the user to discard, apply, or merge the changes.

Merging being the listing of each field showing the recovered & current values and allowing the user to select which values are to be preserved in the next version of the entry.