Root > Compatibility > 5.x -> 6.x > EurekaLog 6 Documentation > Unsupported applications

Unsupported applications

Previous pageReturn to chapter overviewNext page   

Caution: this is old EurekaLog 6 documentation. This is not the latest version.


EurekaLog support natively more applications types (see "features" topic for further details), but not all exists applications types, so the scope of this little tutorial is explain how to can use EurekaLog in unsupported applications types.


Basically the steps to do are two:


create a OnException event for the application type (used to call EurekaLog manually);
create a ExceptionNotify event for EurekaLog (used to customize the EurekaLog behavior).



NOTE: handling Web application you must disable the "Show Exception Dialog" option to inhibit the Exception Dialog showing.



So a little example (to manage unsupported Web modules) can become as follow:



// Event uses to call manually EurekaLog...

procedure TWebModule1.WebModuleException(Sender: TObject; E: Exception; var Handled: Boolean);


  Handled := True;

  StandardEurekaNotify(E, ExceptAddr); // Call manually EurekaLog



// Event used to send to Browser the EurekaLog error page...

procedure TWebModule1.EurekaLog1ExceptionNotify(EurekaExceptionRecord: TEurekaExceptionRecord; var Handled: Boolean);


  Response.Content := GenerateHTML(

    EurekaExceptionRecord.LogText, // Exception Log plain text

    True);                         // Add the JavaScript 'back' button at the page bottom





Send feedback... Build date: 2022-01-17
Last edited: 2018-06-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: