I decided this weekend to tackle the mess that became the Macro Group and macro names within Keyboard Maestro and its supporting Python Scripts and folders.
I recognize that there is no right or wrong way of doing this but I read a bunch of post on this forum and elsewhere (thanks o all) and came up with the following:
As a follow up -- because I want to make sure that I fully understand -- are you suggesting that this be added to i) Axis Decision Tree ii) the Decision Checklist or iii) both. I am not sure where you suggest this be added.
I'd assume everywhere you've got an "Activation -- when can this fire?".
Obviously you could put a "never trigger when Terminal is frontmost" macro in a Macro Group called __Excel__Mail__Teams__Word_Outlook__Safari__Adobe__Finder__Keyboard Maestro__Preview__Pages__Numbers__TextEdit... but that name might be a little unwieldy... __-Terminal is a lot easier
Attached is an updated Reference Card which includes not only your suggested edit but an additional case / condition I noticed when cleaning up my macro groups and names; specifically, when an application must be running when it is not frontmost but not at all times.
The case / example for is the Caffeinate macro we worked on while ago where the macro runs when Teams is running but not necessarily frontmost to account for screen sharing situations (where the shared application is frontmost, think Excel, Word, etc.). This is the added case (I hope I have described it clearly enough).
The updated tear way sheet is below for anyone interested:
