WinActivate doesn't mean Window is Forefront?

[ZiggyStardust]

I am having a bit of a problem. I am writing a script where the user just need to stare at and watch what the script does un-interrupted and have full view of what is going on. There is a case where a "Chat" Window will pop up and block the view. This chat Windows is evil. I can not push it to the background and WinActivate will not bring my Window to the foreground.

I was mistakenly under the impression that when I did a WinActivate and it was a success that my Window would be in front. Not the case. My Window is active but this bleeding chat windows is in front.

How can I tell if another Windows has popped up in front of mine and how can I get the handle to it so I can close it?

Here is the documemtation on WinActivate and it is exactly what is happening:

Remarks

You can use the WinActive function to check if WinActivate succeeded. If multiple windows match the criteria, the window that was most recently active is the one activated. WinActivate works on minimized windows. However, a window that is "Always On Top" could still cover up a window you Activated.

Edited July 4, 2012 by ZiggyStardust

[JohnOne]

However, a window that is "Always On Top" could still cover up a window you Activated

Did you read and understand this?

WinSetOnTop() might be something you should look at.