Hello, @Nr.5-need_input,
After reading your last post and rereading your prior posts in this thread (#19, #23, #25), it's now clear to me that you are providing four categories of feedback:
- Misunderstandings about the macro design
- Suggested macro changes
- Keyboard Maestro Editor behavior
- Macro behavior that is not working as designed (on your mac(s))
1. Misunderstandings about the macro design
No, when selecting the Console button the macro is designed to open Console.app and find the failure/timeout displayed in the macro dialog. Once this is completed, the macro cancels itself and Console.app should be in focus. This is demonstrated the OP, Video #2.
Similarly, when selecting the Action button, the macro will complete the respective task and cancel itself. In this case, the Keyboard Maestro editor will be in focus. See the OP, Video #3.
On a related note, suppose you are viewing the fifth from last failure/timeout in the macro dialog (in this case the dialog would indicate: LATEST-5) and you press the Console button. As described above, the macro would do its prescribed tasks and cancel. If you'd like to restart the macro initially displaying the fifth from last failure/timeout, you can use the alternate hot key trigger (one that includes ⇧) or start the macro from another (or Alfred) and specify Recall in the With Parameter.
2. Suggested macro changes
I addressed this suggested change above in #24.
Generalizing the macro to allow easy modification of the window positions is not something I'm planning to do. But you'll see in the above post, I did provide the actions that you could modify if it becomes a priority for you.
3. Keyboard Maestro Editor behavior
Actually, the syntax that I'm using is one of the permitted variants. You'll see this mentioned in the wiki (Variables).
You can also use a short form of just %Variable Name% to include variables as long as the variable exists and has a value and there is no corresponding text token, although generally it is better and clearer to use the longer form %Variable%Variable Name%.
I don't normally use the short form, but I make an exception for the Set Dictionary Value action. Regardless, you see the same Set dictionary field appearance when you use the longer form.
4. Macro behavior that is not working as designed (on your mac(s))
Above in #24 I started to address your observed issue. There I mentioned that I'm not able to reproduce the issue you are seeing but suggested that you run the following AppleScript in the Script Editor (or Script Debugger) and see if the Help window closes.
( expand / collapse )
try
tell application "System Events"
tell application process "Keyboard Maestro Engine"
tell (first window whose name is "Keyboard Maestro - Display Text")
tell (first button whose role description is "close button")
perform action "AXPress"
end tell
end tell
end tell
end tell
end try
The above AppleScript is what is being used currently in the macro.
Here's another similar script that I've successfully used elsewhere and just tested in the macro. It worked as expected. I suggest that you also try it.
( expand / collapse )
try
tell application "System Events"
tell application process "Keyboard Maestro Engine"
tell (first window whose name is "Keyboard Maestro - Display Text")
tell (first button whose title is "OK")
perform action "AXPress"
end tell
end tell
end tell
end tell
end try
Okay, thanks for the link. From there here's a third approach that works in the macro but but is slightly more complicated because it does require a Type a Keystroke action after the Execute an AppleScript action.
Here's the above AppleScript code:
( expand / collapse )
try
tell application "System Events"
tell application process "Keyboard Maestro Engine"
tell window "Keyboard Maestro - Display Text"
tell button "OK" to set focused to true
end tell
end tell
end tell
end try
If none of those work, then maybe there's some strange interaction that is occurring on your mac(s). Worst case scenario, close the Help manually. 