Berend Veldkamp

Fair point about KP not knowing in advance which window will take focus. I think listening to the WM_ACTIVATE notification could solve this, the lparam references the application being deactivated, which I think is the one that would take focus later.

Yes, that's what I do when I'm not certain which is the target window. But still, it is an extra step to activate the target (again), and then return to KeePass, so if possible, I'd like to skip that. Sometimes when I'm 100% sure the target window is the one I think it is, it turns out to be another one after all. How this happens I don't know, maybe I got distracted, maybe I am just clumsy ;-) Sure, this doesn't happen very often, but when it does it's annoying at least. At one time I even managed...

I'm not sure I understand what you are saying. For now, I'm just trying to make a feature request for something I think is not unreasonable to ask. If it's technically not possible or otherwise unwanted, I'd like to hear it.

That doesn't look too difficult to me. When looking at the source code, it sure seems as if KeePass already uses GetForegroundWindowInfo to determine the (top-most) target window when auto-typing. If that information is present, it would be trivial to get that window's title. The only thing is that the information must be retrieved earlier, i.e. when the context menu, or the toolbar button's tooltip, is shown. There may be things I haven't though about, but right now I don't see any major hurdles...

That doesn't look too difficult to me. When looking at the source code, it sure seems as if KeePass already uses GetForegroundWindowInfo to determine the (top-most) target window when auto-typing. If that information is present, it would be trivial to get that window's title. The only thing is that the information must be retrieved earlier, i.e. when the context menu, or the toolbar button's tooltip, is shown. There may be things I haven't though about, but right now I don't see any major hurdles...

That doesn't look too difficult to me. When looking at the source code, it sure seems as if KeePass already uses GetForegroundWindowInfo to determine the (top-most) target window when auto-typing. If that information is present, it would be trivial to get that window's title. The only thing is that the information must be retrieved earlier, i.e. when the context menu, or the toolbar button's tooltip, is shown. I'm not saying it's trivial, but right now I don't see any major hurdles either.

Ah, now I get what you mean, but that window only shows when using the global auto-type hotkey (Ctrl+Alt+A), not when starting auto-type from within KeePass. And it will only show entries that are somehow associated with the current window. For instance, if I try this in Notepad, the list of entries will be empty. My usual workflow is: If I need auto-type, press Ctrl+Alt+K to activate KeePass Search an entry Press the auto-type button on the toolbar or right click an entry and select one of the Perform...

I tried that option, but all it seems to do is show some sort of tooltip when auto-type is already in progress. Actually, I'm not even sure what this option is supposed to do, sometimes the tooltip just flashes for a split second, sometimes, nothing is shown at all. Anyway, I would like to see where typing is going to take place before clicking the button, so my question was really meant to be a feature request ;-) Is this the place to post those?