hi Jared,
thanks for your response.
the use case for me would be exactly as was stated by the original post: i.e. to be able to parse the current log for messages of tested apps that are not responding anymore and be able to kill them explicitly or simply stop the execution of the current test.
you write:
As for OnLogError, I'm not quite sure why you would need to parse the entire log in its handler because all the information on the error currently posted is available there, and it allows you to process all errors as they occur without missing them.
exactly that would be my question: HOW do i access/parse the text of the currently written log error ? actually, i don't want to read the entire log, only the current log item that led to the error. is there a way/command to do that ?
it's just that sometimes an application returns a specific window with an error that i would like to catch and handle differently than all the rest. e.g. write something into a file when this happens etc.
thanks & best regards
martin
