Can a Keyboard Maestro Macro Programmatically Trigger a Conflict Palette?

I am trying to understand whether a Conflict Palette can be invoked from within another macro.

I have several macros that all share the same hot key trigger, for example Control + F1. When I press Control + F1 on the keyboard, Keyboard Maestro correctly shows the Conflict Palette and lets me choose which macro to run.

However, when I try to simulate this from another macro by using a “Type a Keystroke” action set to Control + F1, the Conflict Palette does not appear. Instead, nothing happens or only one macro runs.

My goal is to be able to press a different trigger, or run a macro, that brings up the same Conflict Palette that would normally appear when I physically press Control + F1.

Is there a way in Keyboard Maestro to programmatically invoke a Conflict Palette, or are Conflict Palettes only triggered by physical keyboard input? If this is not possible, what is the recommended design pattern for achieving similar behavior?

I am happy to restructure my macros if there is a better approach than relying on Conflict Palettes for this use case.

I think I can accomplish this with %TriggerValue% but not certain.

If it were me, I might make a smart group for all macros with the ⌃F1 trigger, and then use the show palette of macros action calling that smart group wherever needed.

That is a pretty cool solution I didn’t know that action could show Smart Groups. It will make for a longer list on the left side of Keyboard Maestro. Still hoping that one day @peternlewis will allow these to be put into subfolders. How is my List is pretty gnarly long on the left with 100+ groups and folders.

100+ … :scream:

How you manage all these?

And how you remember what did you - my main problem with written scripts is that 2 weeks after create one I forgot that I did it (and sometimes start writing it once again :rofl:).

Wrong Action -- use the "Trigger Macros by Hot Key" Action instead, it'll work exactly as you want.

2 Likes

I just did that. I created a quicky "alarm clock" because my phone is dead and, after I had it working, when I did a search to find which group I'd put it in the day before, I discovered that I had two other "alarm clock" macros, each in other groups.