Control: tag 700014 + confirmed
I'm working on updating the pacakge to keepassx version 2.0, which has
a completely rewritten codebase. Unfortunately, this version exhibits
the exactly same behavior as the James reports: The "lock database
after inactivity" fails if there are unsaved changes.
The obvious question however: What behavior do you expect in this
case? Do you expect keepassx to automatically save your pending
changes? What if you didn't mean to save them, or even accidentally
overwrites unintentionally?
My personal opinion is yes, I keepassx should automatically save. But
not only on inactivity, but every time an entry is modified, that is,
as soon as the entry dialog is closed.
Best,
Reinhard
--
regards,
Reinhard
