I'm experimenting with the KM application switcher, and wondering if it's possible for it to stay on screen until I've clicked an application instead of disappearing when I release the assigned hot key.
I know there's the Applications Palette as well, but that's far less configurable visually and has to be explicitly dismissed/toggled.
This doesn't appear to be possible, but I wanted to check in case I've missed something.
I don't know of an official way to do that, but I can make it work on macOS Mojave with Keyboard Maestro 10.2 by using a second macro to execute the app-switcher macro.
(App-Switcher macro not included.)
You can also get the App-Switcher to stay on-screen if you're fast enough on the draw with its keyboard shortcut, but this is difficult to do reliably.
What Chris says, I can confirm for Monterey too. I open the KM app switcher with a palette and can navigate with j, k etc in the window (VIM style). Enter activates an app and esc closes the window without selection. I think this works with all macos.
I'm on Monterey with KM 10.2. Is there anything I'm missing that should allow this to work without having to either hold the hotkey, or get lucky with speed?
Interesting -- only that appears to happen if you use more than two modifiers in App Switcher hotkey trigger. Solution -- fewer modifiers!
Edit to add:
Second solution -- it seems to be the release of the keys that closes the Switcher. Whack in a brief pause before activating it and you can release the trigger keys before the Switcher appears, avoiding the problem entirely.
You'll have to tweak the pause length to suit, or maybe replace it with a "Pause Until...the modifiers are not pressed" action
...although I don't have Hyperkey (which I assume is why you're using such a finger-twisting hotkey) so can't test.
Thanks for the help, everyone! Adding the pause as @Nige_S mentioned, I could keep the hyperkey-based activation with the ton of modifiers and have it still work.
It's interesting that the number of modifier keys affects the behavior. I would not have expected that, but my own experimentation on Monterey backs it up. Overall I don't think I realized until now that it's not as simple as it seems to build and run these macros. Need to change my mindset a little bit.