Console application - internal autoit error trap

[aiter]

I am running my compiled application as a console application and need to prevent any internal errors from being displayed as a gui message, but rather display it as a console message only. An example of such an error would be a bad array reference (out of bounds).

Does anyone know how to do this or point me in the right direction?

[AutoBert]

Have a look at:

i never used it and i suggest avoid errors by good coding practice: https://www.autoitscript.com/wiki/Best_coding_practices

Edited September 19, 2016 by AutoBert

[aiter]

Thanks AutoBert.  Having looked at it briefly, it still returns the error as a dialog though and not console output.  Anything that returns an input response from my console application will cause it to hang because it is called within a framework that requires no input

eg from framework

Execute myapp capturing output

myapp is the compiled autoit script. As soon as myapp contains an input response, myapp hangs within the framework. Thus the reason for no dialogs required, just a console output message saying something like 'An error occurred'.

Edited September 19, 2016 by aiter
spelling

[aiter]

I need to create a real console application.  That means no gui windows opening on internal errors.

I compile with the CUI checkbox checked, but when I run the program from CMD and there is a internal error like array out of bounds, I get a gui window detailing the error.

This is not a true console application then.

How do I create a real console application which shows errors written to STDOUT?

Any help appreciated.  This problem could kill all my work on my project.

[Melba23]

aiter,

Stick to just the one thread please.

M23

[aiter]

Can this be added as a enhancement or bug for autoit please.

Compiled as CUI (console) means console output so output information to console and not as GUI output.

Alternatively have another checkbox for the information 'Error output to console only?'

Thank you amazing AutoIt developers in advance.

 

[aiter]

How about wrapping the call to the program in c++ code ( or autoit code) which looks for that error window in a timer then if found, closes it and terminates the executable?

Before it closes the window maybe it can get the text from the window to output as a console message after it closes that error window and closes the exe.

Does this sound feasible and can anyone help with example code?

 

[aiter]

Approach above worked. Thanks for all the help  Much appreciated.