George ---
The Windows call itself is SetWindowsHookEx(). You should
read up on the hooks WH_KEYBOARD and WH_KEYBOARD_LL.
This is a VERY powerful API. Make sure you can trust the
module that executes this Windows call on your behalf!
I'm not aware of one but there's no reason one couldn't exist.
Both the Shortcut key and macro approaches don't quite
give what I need. I intend a persistent process
maintaining state (including all copy-buffer contents)
continuously. I could have a shortcut-launched
program read in and write out the data at every
invocation, but that would be a very
resour
