SetForegroundWin requires an argument, the name of the window.

Isn't that generating a red error message? It should.

You would think (judging from the name) that SetFocus is the right command, but I took the names "SetFocus" and "SetForegroundWin" from the operating system API, and those names have peculiar meanings in the API. Their meanings got sort of screwed up when Microsoft added multithreading to Windows. It's a long complicated story but the bottom line is, SetForegroundWin is the right command.

If it still doesn't work make sure "Clear modifiers before executing hotkeys" is checked on Settings. (This is for diagnostic purposes). If that works and you want that setting unchecked I'll tell you a way to do that.