The required entry is not selected when multiple databases are open and the database containing this entry is not active. This occures both by using hot-keys or by using {SHOWENTRY} placeholder.
So the proposition is to activate the required database tab.
Last edit: kibinimatik 2018-03-17
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm sorry, I'm not sure what you mean by the icons getting mixed. The only change I made was to specify which database should be made active by KeePass, so it shouldn't be affecting any icons...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When an entry or a group of the target database has a custom icon it gets displayed incorrectly: without its icon or with a wrong icon. Please, see the attached video
No, 0.3.1 is fully released. Sourceforge doesn't seem to have automatically tagged it as the latest release, though, it still lists 0.3 as the latest. I'll investigate.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The required entry is not selected when multiple databases are open and the database containing this entry is not active. This occures both by using hot-keys or by using {SHOWENTRY} placeholder.
So the proposition is to activate the required database tab.
Last edit: kibinimatik 2018-03-17
I agree, thanks for suggesting it. I will release a new version with this functionality soon.
v0.3 now released, which will behave in this way.
Thanks!
But something is wrong: when the tab is activated the icons get mixed.
I'm sorry, I'm not sure what you mean by the icons getting mixed. The only change I made was to specify which database should be made active by KeePass, so it shouldn't be affecting any icons...
When an entry or a group of the target database has a custom icon it gets displayed incorrectly: without its icon or with a wrong icon. Please, see the attached video
Last edit: kibinimatik 2018-03-17
Thanks, that's helpful. Could you give the attached 0.3.1 a try, see if that resolves the issue for you?
So far the 0.3.1 works properly, many thanks!
Great, thanks for letting me know. I'll release that now.
The version 0.3.1 is still marked as pre-release. Is it correct?
No, 0.3.1 is fully released. Sourceforge doesn't seem to have automatically tagged it as the latest release, though, it still lists 0.3 as the latest. I'll investigate.