OK, given that you want to also capture the keystroke, it may be simpler, better, to use something like this:
-
MACRO A
- The initial macro that starts your workflow.
- Does whatever you want until you want it to "pause" for any keystroke.
- Then it would enable Macro B, and exit.
-
MACRO B
- Is initially disabled, until enabled by Macro A.
- Has a typed string trigger of
\.
- If you can restrict your keystroke to letters or numbers that would be better
- You could then use
\w
(any letter or number)
- As soon as you type a keystroke, this macro is triggered.
- The key pressed is in the token
%TriggerValue%
- Do whatever processing you need with it
- Then disable this macro as the last Action
There may be other, better, approaches.
How does that sound?