Forum Discussion
Yshippin
13 years agoContributor
I ussualy use something like Process.FindChild("WndCaption", "*Error*",1) for an expected / possible error window, and if it is an unexpected window TestComplete knows how to post an error message to the log and get around it.
But if you insist on using ActiveWindow you could set focus on the window of your application before checking the active window, error messages are set to be "always on top" of your application's window, so it will automatically become the active window after setting focus on your application..
But if you insist on using ActiveWindow you could set focus on the window of your application before checking the active window, error messages are set to be "always on top" of your application's window, so it will automatically become the active window after setting focus on your application..