When I call SetActiveWindow on any maximized window, it unmaximizes the window. I have a dual monitor setup, so I can play my game maximized (not fullscreen, just maximized like any other app) and run ACtool on the other monitor. But when I call SetActiveWindow it unmaximizes the window, and it takes several seconds for the game to recreate all the directX buffers.

Is there a way to set it up so that it sets the active window as if I just clicked on the title bar?

Run both from same monitor

I usually just re-maximize it (though it may or may not be helpful in your case).

Example:

That's really a non solution, isn't it? lol



It takes several seconds for the game to rebuild its DirectX buffers if you change its resolution, so this isn't really practical.

...


How is alt tab behavior set up? Would there be a way to emulate it (not the alt tab keystroke, although that's might be an interesting avenue...)?

I've found that it works out ok for many games/applications as long as the window is re-maximized immediately after it's minimized by AC Tool.
That's why I suggested it.



Regarding Alt+Tab:

I don't know of another way to emulate Alt+Tab other than keys @{tab}
Which will take you to your game window as long as it's next to AC Tool on the taskbar.


I've had several macros that didn't use SetActiveWindow at all, and I don't recall there being any problems.

At few years back, not using SetActiveWindow would automatically set Asheron's Call as the active window.
I don't know if that's still the case, or whether or not it even matters.