Jump to content

Recommended Posts

Posted

You could, as long as you know the ProcessID of the process, and the title/class/text of the error window, using this function:

WinGetProcess

Something like:

If WinExists("Error window") And WinGetProcess("Error Window") = $ProcessID Then
...
EndIf
Posted

what if you dont know the title/class/text of the error window.. is there any general way to just check if another window has come about from a PID..??

Posted

So the error window has no title or text that always stays the same when it tells you an error has occurred?

If not, then the only thing you can do is to track what windows the process has, and do something if it creates another window..

Posted

Handles are not static(like class names, or titles, etc.), so he would have to store all existing windows for the process(during runtime), then compare them against the list to find out if any new window was created. But that still doesn't tell him that just that window that the process created is an error window...

I find it somewhat unlikely that the process creates a window, with no sort of static message declaring that an error occured.

To the OP:

Can you show us a screenshot, or a text snip of what the window contains/looks like? :)

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...