|
|
You can click on the tabs in the left side of the image:
You have two possibilities how a bug report can be saved: You can specify only a file name or a full file path. If you only specify a file name and the user then presses the "save bug report" button, madExcept opens a "save as" box. If you only specify a file name and the bug report shall be be saved automatically, it's saved into the same folder where the current process' executable file is stored. If you specify a full path, no "save box" is shown, even if the user presses on the "save bug report" button, instead the bug report file is directly written to the specified path. You can specify what you want to happen if the bug report file already exists. The new bug report can overwrite the old file, or the bug report can be appended to the old file. In the latter case you can specify how big the bug report file may get. If it gets longer than that specified limit, some of the oldest bug reports are deleted from the file.
By default madExcept doesn't save "duplicate" bug reports. That means if the bug report file already contains a report about the exception which just occurred, madExcept just increases the "count" header field of the saved bug report. If you prefer having all reports fully saved, you can turn the default behaviour off.
When are 2 exceptions identical? What if the exception location is identical but the callstack is not? Do you see that as identical enough or not? Since your mileage may vary, you can tell madExcept what your understanding of "identical" is.