This is "Advanced/Exception filters" page in EurekaLog project's options.
Exception filters options
This page allows you to set up exception filters. Exception filter is a filter which can alter EurekaLog's behavior based on some properties of exception. It is a easy way to customize EurekaLog on per-exception basis without writing code.
Important note: you can not use exception filters to alter behavior for leaks (e.g. EMemoryLeak/EResourceLeak), because exception filters are already finalized when leaks checking is running.
1. "Activate Exceptions Filters" (.ActivateFilters) option enables or disables exception filters globally. Exceptions filter below will have no effect when this option is disabled.
2. "Exception Filters" (.ExceptionsFilters) option defines one or more exception filter.
Usually exceptions are identified by exception's class name. You can also identify exception by source location. And you can identify exception by its type (handled or unhandled). Once exception is identified - you can change handler for it (none, RTL or EurekaLog), dialog class (to any of existing dialog classes), override error message or set action (restart or terminate). Exception filters are applied before processing exception. Filters are applied in order from top to bottom. First matched filter is applied.
When exceptions filters are not enough - you have to write code (event handlers).
Note: sometimes it's more easier to use custom attributes instead of exception filters.
Important note: ensure that features specified in exception filters will be available at run-time. For example, if your application uses MS Classic-styled exception dialog by default and you want to switch to EurekaLog-styled dialog for some exceptions by using exception filters - then be sure to include code for EurekaLog dialog into your application.