Nice report! It certainly happens locally on a debug build. pwsafe\src\ui\Windows\MainEdit.cpp Line: 182 This is the assertion. // Now select item DisplayInfo pdi = GetEntryGUIInfo(iter->second); ASSERT(pdi->listindex != -1); SelectEntry(pdi->listindex); Looks like the problem is that the newly created entry does not become visible because of the active last find results.
Normally the dialog from the first screenshot (no drop-down, fixed file) appears when I already have pwsafe running and the database is locked. In other words, this is the dialog to unlock the already opened database. And if I start pwsafe fresh, then I see the dialog with the dropdown to choose a database from the recent list. Is it possible that this is what happening? Super weird otherwise.
Hey @gillum, could you please share the exact sequence of step to reproduce what you see with 3.60? Possibly another issue.
On Windows, the context menu comes up when you do an alternative mouse click (right if left is your primary button) on an entry.
Got it. Indeed, the order is Password, Username in the main menu and on the toolbar. But it is Username, Password in the context menu. I am totally in favor of making the order Username, Password everywhere. I can make this change. @ronys, what do you think?
Ah, I see. Indeed. I solved this problem (without actually thinking about it too much) by putting every password or key in a separate entry. For example, I have a group for the router, and this group has individual entries for admin login, wifi networks, etc. This way I almost never have to reveal the password field. Some information still goes to the notes, of course. But the remaining information usually is needed very rarely. I will let the maintainers think about the proposed highlight change...
Oh, and yes, you can change the shortcuts in Manage - Options - Shortcuts.
Hey Dave, Re: Second feature Did you know that you can copy the old password by clicking the corresponding row in the history? It looks like exactly what you asked, doesn't it?