#4 TOTP does not remember user configure column setting

[wellread1]

The TOTP display column setting reverts to ON so that any time a user opens the KeePass configure columns dialog the TOTP column will revert to showing unless the user remembers to uncheck the show column check box. This is a problem for two reasons:

1. The plugin should honor the user's express intentions by remembering this setting state.
2. Until the issued in ticket 3 is fixed, the TOTP plugin renders KeePass auto-type unusable for larger databases, except when the TOTP column is hidden.

[wellread1]

I have subsequently determined that this issue manifests only when another plugin that creates a column is present. Since I don't have the skills to determine whether the cause is KeePass or one of the plugins I am reporting in both relevant forums.

I have installed two plugins that create columns under "Created by Plugins" section in the Configure Columns dialog:

Quality Column 1.2
Tray Totp 2.0.0.5

Problem in KeePass 2.25:

• If a user selects one plugin created column for Display in the KeePass Configure Columns dialog, the column is correctly displayed. However if the user closes the Configure Columns dialog then reopens it, both columns are selected for display. If the user takes no action both columns are displayed when the Configure Columns dialog is closed.
• If a user selects or deselects both columns, the column display settings are remembered correctly.
• If either plugin is installed by itself column display settings are remembered correctly.

[Morphlin]

Hello wellread1,

First of all, I want to thank you for not giving up on me. I've had very time to spend on any thing else than school and work and both are completely unrelated to programming.

For this ticket, I can assure you that my plugin does not affect KeePass's settings. When you choose to display a column, it is saved in KeePass's settings which are isolated from the plugin.

I will look into ticket # 3 as soon as I can.

Thanks

Morph

[wellread1]

This ticket can be closed.

The problem was caused by KeePass and will be fixed in KeePass 2.26.