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
Observations made using current YAFD 1.2.5.0 on KeePass 2.5.3
KeePass shows the database as modified ("Save" icon changes to blue, and exit will produce the warning to save changes) even if downloading favicons finds no icons at all.
This behavior is notwithstanding the mods for #35 and #68. The changes for #35 to provide a config choice whether to "Update entry last modification time" appear to only impact the timestamp recorded on the "Modified" timestamp in the password entry's History tab. Additionally, if I have "Update entry last modification time" enabled, then the password entry's Modified timestamp gets updated whether or not an icon was found.
All this suggests that something gets written to the KeePass database any time a search is conducted, regardless whether the search finds any icons, and regardless the setting of Update last mod time.
The text was updated successfully, but these errors were encountered:
Observations made using current YAFD 1.2.5.0 on KeePass 2.5.3
KeePass shows the database as modified ("Save" icon changes to blue, and exit will produce the warning to save changes) even if downloading favicons finds no icons at all.
This behavior is notwithstanding the mods for #35 and #68. The changes for #35 to provide a config choice whether to "Update entry last modification time" appear to only impact the timestamp recorded on the "Modified" timestamp in the password entry's History tab. Additionally, if I have "Update entry last modification time" enabled, then the password entry's Modified timestamp gets updated whether or not an icon was found.
All this suggests that something gets written to the KeePass database any time a search is conducted, regardless whether the search finds any icons, and regardless the setting of Update last mod time.
The text was updated successfully, but these errors were encountered: