I can’t figure out how to get the commands from a custom macro group to appear in the status menu when the palette is closed. To clarify: I DO want those commands in a palette, but I also want them in the status menu for when the palette isn’t active.
Usually I prefer to access commands from the status menu (or hotkeys), but there are times when it’s more convenient to have the palette open. Other times the palette clutters my workspace so I want it closed, but I still want access to its commands with the status menu or hotkeys.
If this isn’t currently possible (and from what I gather, it is not unless I create duplicates of my macros with different settings), I would like to add a wish-list item for the option of having commands available from the status menu whether the palette is opened or closed.
Perhaps a new status for a palette: “Hidden”. So along with Active/Inactive, Enabled/Disabled, there could be Visible/Hidden.
1 Like
I would prefer that another option be provided in the macro activation section that allow it to be triggered whether or not it is in a visible palette.
I have lots of macros that I want always available for a specific app, but I also want them in a palette for easy reference.
I agree with @veramilo, if the "Status menu item is selected" is one of the macro triggers, the macro should appear in the menu regardless of whether or not the palette is shown.
Yeah, you make a good point. OK, I agree with you. 
Currently, a macro group that shows a palette is active if and only if the palette is displayed.
A case can clearly be made for allowing a macro group to be always active and show its palette sometimes, but that is not currently an option.
The only current way to do this is to have the macro group always active, and have a second macro group which shows a palette and which has a macro for each macro in the first macro group, each of which does an Execute Macro on the first macro.
2 Likes
I agree. That's exactly what I decided to do. It's not horrible. 
If both sets of macros use the same hotkeys, wouldn’t the conflict palette pop up? I tend to use hotkeys much more than menus so the #1 reason I’d like them to appear in both places is to help me learn them.
If I could only have the hotkeys in one place in order to avoid the conflict, my choice would be the palette since it can stay visible longer than a menu and give me more opportunity to learn the hotkeys. But then I’d be back where I started: The hotkeys only work when the palette is active.
I do, however, like the idea of macros in a palette group “executing” macros in another group. At least I wouldn’t have to update two sets of macros when I have changes. But I still hope a future KM update offers an option to trigger macros even if a palette is closed.
BTW: I have only been using KM for a few days. Being a long-time Quickeys user (over 20 years) and having grown dependent on it, I was upset when it was no longer supported and began degrading with each new OS release. I’ve tried adapting without it (only a handful of my shortcuts work anymore) for a couple months now, but I can’t. I was thrilled to finally find a more than suitable replacement. Thank you!
What I do is have hotkeys on the non-palette group, since it is always active. The palette doesn’t really need them, because the non-palette group takes care of that.
In the palette group, I show the hotkeys in the name of the macro, within parens, like “Get Help (F1)”.
1 Like
I considered doing that, and I still may. For now I’m just going to set aside using the palette and hope for a future update as I work on recreating my macros from QK.
1 Like