You got the idea. I do not need a screen shot, just information from the pop-up window. I believe somewhere in the CVI there is a global function active only in debug build that doing something like this:
if(error) {
PopupMessage(error, filename, line);
exit();
}
What I am looking for is the way of doing something like this:
if(error) {
PopupMessage(error, filename, line);
if( userfunc!=NULL )
userfunc( error, filename, line );
exit();
}
Where userfunc() will be user definable call back function that will perform whatever I will put there. This will be very usefull because will not require chaning existing code - in contrary with the chkNull or assert macros approach.
I worked with different languges (mainly MS C/C++/C#, PHP) - all of them have some sort of a "hook" when you can set callback function that will be called in case of something like "unhandled exception" (in terms of C++/C#) will happen. This function usually has access to the error information, so I can record it. The great things is that if I have binary file (EXE or DLL) compiled with debug information available (same is for CVI) it can point right into the line of source code where the error happened.
Screen shot will not work well here:
1. It is hard to require operators be able do something like this. Sometimes it is also imposible to wait until somebody available who can make it.
2. Automation does not work either, because how I would know when the pop-up appears?
I was thinkng of the way to subclass window function (using Win32 API) for the error message box or something like this, but stiil not found the right way to do it.
