I have an Excel password using the "Option A" to trigger, entering the password. It works ok with "Command A" and "Control A" but not "Option A" Is their a conflict the system using "Option A". Using Sequoia. Any guidence would be helpful.
If you haven't already, update to macOS 15.2
Apple decided to disallow Option- , Shift-, and Option-Shift shortcuts for sandboxed apps (using those with Command or Control is still OK), and it looks like Excel's password request routine is sandboxed.
The decision was reversed with the 15.2 update so, hopefully, that'll sort your problem for you. If not you'll have to go with a different modifier for your trigger.
1 Like
Is the macro triggering but the wrong thing being typed? If so, the reason follows:
In a password field (any time Secure Input Mode is enabled), Keyboard Maestro (or any other application) cannot see the state of the keyboard.
So, for example, you cannot use a Typed String trigger inside a password field.
If you trigger the macro with the hot key, then the keys you are pressing are currently held down (in this case, that specifically includes the option key). But crucially, Keyboard Maestro cannot see that the option key is down. So when it goes to type the password, it does not know it needs to release the option key in order to type correctly. So keys will have the option key pressed which will mess up what is typed.
The same thing will happen for any character A in the password - Keyboard Maestro cannot see that the A is pressed, and so does not know it needs to release the A before typing the A, resulting in the first A in the password being missed.
Normally, the solution would be to use a Pause Until action with the Key condition and wait for the keys to be released - but of course this does not work since Keyboard Maestro cannot see the state of the keys.
You can start the macro with a short pause, and ensure you release the keys before the pause expires, or you can choose a different hot key, or a different trigger (eg the Status Menu trigger).