Well, searching the forum shows 7 pages for the "autosave" request.
I wonder, why is that KeePass still doesn\t have an autosave function? I don't think it's so hard to check the DB state and save if it's unsaved on regular user-defined time frames.
Well, if it is not considered as a good feature, i'd like to have the "Time frame" switch in the Triggers/Events list. So i could use it with the "Database unsaved" condition to autosave my unsaved work, lets say, every 5 minutes.
But again, it leads to the question in my other thread: what if i just edited my passwords in the comments field(i use it for the extra passwords for the projects, like WP,SQL,FTP, so on, for the same site) and KeePass does not recognize the DB as beeng edited?
Last edit: Ulrikhe Lukoie 2016-02-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You could file a feature request. I suspect such an trigger action creates complexity in execution or implementation that the developer prefers to avoid because this could have been implemented in the existing "Wait" trigger action but wasn't.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, searching the forum shows 7 pages for the "autosave" request.
I wonder, why is that KeePass still doesn\t have an autosave function? I don't think it's so hard to check the DB state and save if it's unsaved on regular user-defined time frames.
Well, if it is not considered as a good feature, i'd like to have the "Time frame" switch in the Triggers/Events list. So i could use it with the "Database unsaved" condition to autosave my unsaved work, lets say, every 5 minutes.
But again, it leads to the question in my other thread: what if i just edited my passwords in the comments field(i use it for the extra passwords for the projects, like WP,SQL,FTP, so on, for the same site) and KeePass does not recognize the DB as beeng edited?
Last edit: Ulrikhe Lukoie 2016-02-09
See the reply to your other question.
cheers, Paul
So what about "Time frame" switch in the Triggers/Events list?
You could file a feature request. I suspect such an trigger action creates complexity in execution or implementation that the developer prefers to avoid because this could have been implemented in the existing "Wait" trigger action but wasn't.
Why do you need to save every X minutes when you can trigger on unsaved changes (user interface state updated)?
cheers, Paul