You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
i found KeePassXC when searching for alternatives to KeePassX.
Current Behavior
One thing the i have problem with in both, is that whenever i look for certain key, i am bound to fold and unfold several groups. This marks the db as modified, even though no data has been modified.
For me, it is much more important, to be sure i did not accidentally made changes to the DB while navigating it, than remembering that last fold/unfold group state.
It also creates unnecessary conflicts when syncing the DB over machines with unison at the end of the day.
Possible Solution
I guess, in the best case, i would like to see a setting : "group tree on startup all_folded/all_unfolded/last_state"
Or maybe some additional logic, if i unfold a group (dirty flag will be shown as it is now) and when i fold it back the dirty flag disappears, and i can close the DB without seeing save_modified dialog.
The text was updated successfully, but these errors were encountered:
Hello,
i found KeePassXC when searching for alternatives to KeePassX.
Current Behavior
One thing the i have problem with in both, is that whenever i look for certain key, i am bound to fold and unfold several groups. This marks the db as modified, even though no data has been modified.
For me, it is much more important, to be sure i did not accidentally made changes to the DB while navigating it, than remembering that last fold/unfold group state.
It also creates unnecessary conflicts when syncing the DB over machines with unison at the end of the day.
Possible Solution
I guess, in the best case, i would like to see a setting : "group tree on startup all_folded/all_unfolded/last_state"
Or maybe some additional logic, if i unfold a group (dirty flag will be shown as it is now) and when i fold it back the dirty flag disappears, and i can close the DB without seeing save_modified dialog.
The text was updated successfully, but these errors were encountered: