###ISSUE: KM Palette Behavior Has Changed
Running Keyboard Maestro 7.3.1 (7.3.1) on macOS 10.11.6.
The behavior of this Action seems to have changed recently (within the last week):
Now, after this macro/action is run, the target Group is Disabled, and I am not able to trigger macros using hotkeys in that Group. See the below KM Engine.log file below for details.
I have confirmed this behavior with another Macro Group, and on another Mac. I have restarted the KM Engine, and my Mac, which did NOT change the behavior.
Can anyone else confirm this behavior?
@peternlewis, have there been any recent changes to KM that would cause this?
Previously, for nearly a year, I took advantage of this Action in a global macro to show a palette for one action when I needed it, while still being able to trigger macros in the same Group using their hotkey.
Now, the KM Editor display of the Group does NOT change after the Show Palette Action is run. It looks identical before and after. Here's an example:
###Macro to Show Palette for FrontMost App
This is a very simple macro which really uses only one key Action, Switch Case based on the FrontMost app, and then does a Show Palette for the Macro Group for that app.
###Palette Shown by Above Macro
Shows all of the macros in the Group
###KM Engine.log File
~~~ FROM KM Engine.log File ~~~ ~~~ NORMAL TRIGGER OF OL MACRO BEFORE PALETTE ~~~ 2017-07-08 15:17:14 Execute macro ‘@OL FWD to @Evernote (@EN)’ from trigger The Hot Key ⌃⇧E is pressed ~~~ TRIGGER OL PALETTE, AND THEN SAME MACRO ~~~ 2017-07-08 15:17:57 Execute macro ‘@Palette Show/Hide Palette for @FrontMost App’ from trigger The Hot Key ⌃⇧P is pressed 2017-07-08 15:18:39 Execute macro ‘@OL FWD to @Evernote (@EN)’ from trigger Macro Set Palette ~~~ ATTEMPT TO TRIGGER OL MACRO AGAIN VIA HOTKEY ~~~ ~~~ No log entry because Macro was NOT triggered ~~~ I just heard the beep when an invalid shortcut is used