How come the state of the app's DB is not changing from the "unsaved" when i edit the comment field?
I use comment field quite actively on daily basis, and i'd like to save my DB when i finish my edits, but the save button is inactive while i edit the comment field, so i need to switch somewhere to be able to save.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
...the save button is inactive while i edit the comment field,... [emphasis added]
If there are no unsaved changes (i.e. the save button is inactive) when you begin to edit an entry, the save button will remain inactive while you edit the entry. Once you commit to the changes, i.e. press OK, the save button will be enabled.
It may appear that KeePass is not detecting changes if you are using the autosave triggeror a plugin such as KPEnhancedEntryView, because changes are saved immediately (or soon) after they are detected.
Last edit: wellread1 2016-02-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ah right, i use KPEnhancedEntryView
And still, if i edit the notes on the side panel, enhanced by KPEnhancedEntryView, should it be KPEnhancedEntryView who changes the state to unsaved?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Typing alone is not sufficient to trigger the unsaved state. A user action that signals that user's desire to comit a change, combined with an actual change is required to set the state to unsaved; e.g. for the case of KPEnhancedEntryView it is exiting a field where a change was made, while for KeePass alone, pressing OK on the Edit dialog after an actual change has been made in the entry is required.
Last edit: wellread1 2016-02-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When using KEEV and editing a Note in the main window, pressing the Enter key only adds a carriage return to the note. To accept the change, and change the database to "unsaved", you need to click away from the Notes field.
cheers, Paul
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How come the state of the app's DB is not changing from the "unsaved" when i edit the comment field?
I use comment field quite actively on daily basis, and i'd like to save my DB when i finish my edits, but the save button is inactive while i edit the comment field, so i need to switch somewhere to be able to save.
Not seen that one.
Do you have any plug-ins?
How do you edit the Notes?
cheers, Paul
If there are no unsaved changes (i.e. the save button is inactive) when you begin to edit an entry, the save button will remain inactive while you edit the entry. Once you commit to the changes, i.e. press OK, the save button will be enabled.
It may appear that KeePass is not detecting changes if you are using the autosave trigger
or a plugin such as KPEnhancedEntryView, because changes are saved immediately(or soon)after they are detected.Last edit: wellread1 2016-02-09
Ah right, i use KPEnhancedEntryView
And still, if i edit the notes on the side panel, enhanced by KPEnhancedEntryView, should it be KPEnhancedEntryView who changes the state to unsaved?
Typing alone is not sufficient to trigger the unsaved state. A user action that signals that user's desire to comit a change, combined with an actual change is required to set the state to unsaved; e.g. for the case of KPEnhancedEntryView it is exiting a field where a change was made, while for KeePass alone, pressing OK on the Edit dialog after an actual change has been made in the entry is required.
Last edit: wellread1 2016-02-09
When using KEEV and editing a Note in the main window, pressing the Enter key only adds a carriage return to the note. To accept the change, and change the database to "unsaved", you need to click away from the Notes field.
cheers, Paul