Root > Basic procedures > Configuring dialogs

Configuring dialogs

Previous pageReturn to chapter overviewNext page   

This article is a part of basic procedures.


When any error occurs (like unhandled exception or leak) - EurekaLog generates a bug report, which you configured on previous step. EurekaLog also shows an error dialog - it's some kind of dialog or output, which tells the user about error.


You can configure dialogs at "Dialogs" section in EurekaLog project's options.


Usually a dialog is set automatically when you select a type of your application. In some cases you have only single meaningful type of dialog available. But in most cases you can change a default dialog to some other dialog.


Just select a dialog's type from combo box and set additional dialog display options.


There are many dialogs available - here is a short list of available dialogs:



Where applicable



Any application's type

Dialog that does nothing at all. It doesn't show anything. Best suited for non-visual applications.


Any application's type

Standard application's error dialog.


Visual applications only

Displays error message via Windows.MessageBox function.

MS Classic

Visual applications only

Displays error message in MS Windows XP-style dialog.


Visual applications only

Displays error message in EurekaLog-style dialog.


Console applications only

Displays error by outputting it to console (error output).

System log reporting

Any application's type

Outputs error message to system log (event log).


Web applications only

Displays error in returned HTML page.

Windows Error Reporting

Any application's type

Elevates error to OS.


Note: some dialogs have meaning (and can work) only in certain project types. For example, attempt to use console dialog in VCL GUI application will result in error. Other dialogs may require additional setup. For example, a system logging requires you to register an event source for your application. See dialogs for more information.


You can know more about each dialog's options by reading Dialogs descriptions or by clicking on the dialog's link in the table above.


Important: by default EurekaLog is enabled only for the main thread in your application. You have to specify which background thread you want to monitor. Threads created with TThread (or TThreadEx) class do not show any dialog, but save thread's exception into the .FatalException property. You are supposed to handle/process the .FatalException property after thread completes. While this task is not EurekaLog-related, but you can still see some examples here.



See also:

Send feedback... Build date: 2022-03-28
Last edited: 2022-01-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: