id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
2181	WinWaitActive() doesn't necessarily return active window	nf9b9d5ka4@…		"It appears that if there are multiple windows that match the arguments to WinWaitActive() that the handle that is returned may or may not be the active window that caused the function to return.

The instance that I was encountering was that I was matching ""[CLASS:Afx:400000:0]"".  It turned out that while that was the accurate class for the window I wanted to match, there were two other invisible windows (WinGetState=5) that the program had created with the same class, and it appeared that WinWaitActive() was apparently returning one of those instead of the one that was active.  This is somewhat speculative, but it makes sense, and it definitely wasn't returning the correct window.

I've worked around this by following the WinWaitActive() call with a WinList() call and a loop that checks to see which of the windows is actually active.  So far, it's working a lot better, which, again, supports my theory.  But it is just a theory."	Bug	closed		AutoIt	3.3.8.1	None	Rejected