...register event handler from code?

Important Note: NEVER assume thread in which your event handler will run. Your event handler may be called from a background thread even in single-threaded application. For example, a stack overflow exception will force all event handlers to run from a background service thread. Conclusion: always use proper synchronization when accessing global entities from your event handlers.

Using TEurekaLogEvents component is a simple way to register your event handler. However, it is not enough if you want to react to events when form is not created. You can register event handler manually from your code.

You need to include EEvents unit in uses clause. And you need to register your event handler via one of RegisterEventXYZ procedures:

uses
  EEvents;
 
procedure MyExceptionNotifyHandler(const ACustom: Pointer; 

  AExceptionInfo: TEurekaExceptionInfo; 

  var AHandle: Boolean; 

  var ACallNextHandler: Boolean);
begin
  // your code here
end;
 
initialization
  RegisterEventExceptionNotify(nil, MyExceptionNotifyHandler);
end.

You can see a description of each available event here. You are usually interested in the OnExceptionNotify event. OnExceptionNotify event is an OnException-style event.

Each event is represented as method and procedural type - ending in ...Meth and ...Proc correspondingly. For example, OnExceptionNotify event is represented by:

As you may already guessed: method types are used for TEurekaLogEvents component; procedural types are used for manual registration from code. However, nothing stops you from registering method event handler from code too.

Important Notes:

See also: