That is excellent! Thank-you!

Your suggestion definitely works for a compiled macro
Is there a way to get the process id for a macro running within macro scheduler in 'developer mode'?

That's it! Thank-you!

If I distribute a macro with that code in it wouldn't is always just detect itself running? I'm not sure how that would help me see if a previous iteration of the macro was running. Thanks for the idea though!

. When I use OnEvent>KEY_DOWN key combinations that are not recognized by Windows I get an annoying 'beep'. . I can suppress the beep by changing the 'current' default beep in the Registry to 'null' (and then restoring the value that was present when the macro began on exit) but does someone know a ...

. I plan to distribute a compiled macro that contains several OnEvent commands. I need to ensure that the macro is not called iteratively. I was unable to find a better way to determine if the macro was already running so I'm writing a 'pulse' date / time to a .Ini file and and then checking to see ...

Corrected syntax -now it works as expected:

Let>RP_WINDOWMODE=0
/*
PS1:
Add-Type -AssemblyName System.Windows.Forms;
[System.Windows.Forms.Screen]::AllScreens | Clip.exe;
*/
LabelToVar>PS1,PSCmd
Run>powershell.exe -command "%PSCmd%"
wait>10
GetClipBoard>check_ps
**breakpoint**

The following PowerShell commands return the information I need but I'm having trouble getting them to work in Macro Scheduler: /* PS1: Add-Type -AssemblyName System.Windows.Forms [System.Windows.Forms.Screen]::AllScreens | Clip.exe */ LabelToVar>PS1,PSCmd,1,1 Run>powershell.exe -%PSCmd% wait>2 GetC...

. The issue with running the executable using a Windows Hot-Key is that I want to know which window was active when they pressed the Hot-Key and I won't be able to tell which window that was. Using commands to do an 'Alt-Tab' works but I'm not sure how reliable it is. Thank you for the suggestion to...

. The issue with running the executable using a Windows Hot-Key is that I want to know which window was active when they pressed the Hot-Key and I won't be able to tell which window that was. Using commands to do an 'Alt-Tab' works but I'm not sure how reliable it is. Thank you for the suggestion to...

A have a macro for managing / manipulating windows on PC with multiple monitors (similar to Display Fusion but with custom modes not supported by them). I have two 'issues' that I have work-arounds for, but I'm wondering if anyone has better alternatives. 1) I need a way to read the current screen r...

I have used Macro Schedule for years and have not needed OCR functionality until now. Searching this forum I found a few products mentioned but most of the entries were not current. Searching the internet shows there are a large number of products available. If you have used an OCR product with Macr...

Thank-you Marcus - the misspelling of WinTitle_Handle was the issue.
It is truly amazing that I could not see that!

A 'MoveMouseRel' followed by a 'LClick' will be my work-around until I find out why SetFocus doesn't work in this instance.

I add the following statements after the 'Wait>5.00' statement shown in my previous message. GetActiveWindow>tst_title,tst_X,tst_Y,tst_W,tst_H **breakpoint** tst_title is equal to WinTitle_Handle, as if SetFocus worked. But on the screen itself, the window associated with WinTitle_Handle never obtai...