Configure autosave delay per database #8553

spotlesscoder · 2022-10-07T13:40:14Z

Summary

I want a per-database file setting on how long the application should wait before committing confirmed changes into the database file on disk.

E.g. I want to set a timeout of up to 5 minutes so that I can make multiple edits but the changes are saved only 5 minutes after the last edit or when I force saving by pressing CTRL + S

Examples

Context

When performing multiple edits in a row, especially with larger databases, the saving after clicking OK in the detail view, the saving takes quite a lot of time

jNullj · 2023-02-08T22:07:37Z

Can i get assigned to do that? I would love to try.
I belive there is no risk in making this setting part of the metadata and i think it will best fit in General window of the database settings - under the "Additional database settings".
@CodingSpiderFox Wouldn't it be better to save after X minutes since the first change that triggers the timer to avoid data loss? Sure it will lag once in a while to save but you will have more control over the level of risk regarding losing information. That way you still get "forced" into saving once in a while. If i implement the timeout since the last edit there might pass a long time between edits. Altho i agree its nicer to get the app to lag on save only after a few min it is not in use.

droidmonkey · 2023-02-08T22:26:59Z

Yes please do try this

Add a new propery autosaveDelay in Metadata of the db. The propery sets delay to wait since last modification before saving. Part of issue keepassxreboot#8553

Add metadata propery autosaveDelay to the gui in the DatabaseSettings widget under General. User can change the delay in minutes. Part of issue keepassxreboot#8553

Implement a autosave delay functionality to the database widget. Added timer to track the delay and trigger a save on timeout using the new onAutosaveDelayTimeout function. Changed the onDatabaseModified to test for the new autosaveDelay property and delay the save if needed or extend the delay on new modifications. Part of issue keepassxreboot#8553

Try to toggle in gui, set a value, save it. Chcek value saved is currect in metadata. Check that on loading saved value presented in gui and toggeled. Part of issue keepassxreboot#8553

Test autosaveDelay makes delays as expected. Test delay timer reset after new modification before timeout. Part of issue keepassxreboot#8553

Add a new propery autosaveDelay in Metadata of the db. The property is saved in customData to do not affect database structure as this setting is unique to keepasxc. The propery sets delay to wait since last modification before saving. Part of issue keepassxreboot#8553

Add metadata propery autosaveDelay to the gui in the DatabaseSettings widget under General. User can change the delay in minutes. Add new translation strings as well. Part of issue keepassxreboot#8553

Implement a autosave delay functionality to the database widget. Added timer to track the delay and trigger a save on timeout using the new onAutosaveDelayTimeout function. Changed the onDatabaseModified to test for the new autosaveDelay property and delay the save if needed or extend the delay on new modifications. After menual save stop the timer to avoid saving when not needed edited in DatabaseWidget::save(). Part of issue keepassxreboot#8553