Automatic way is a simple "Default EurekaLog state in new threads" option. This option is set to "Disabled (recommended)" value by default. You can change this option to "Enabled" or "Enabled for RTL threads, disabled for Windows threads" states: EurekaLog will be enabled automatically when creating corresponding threads.
Important note: it is highly not recommended to use automatic enabling. Enable EurekaLog manually for each of your threads.
However, the problem with automatic enabling is that EurekaLog will be enabled for ALL threads in your application. Consider a typical multi-threaded application:
Threads in typical multi-threaded application
This simple application has only two threads created by you (your code): a main thread (6688) and one background thread (7952). Your code created background thread to perform lengthy calculations and to avoid GUI freezing. All other threads were created by some 3rd party code:
Obviously, almost all of these threads were launched with some exception handling code in mind. Creator (3rd party code) expects these threads to behave in some specific way when exception is raised in a thread. Injecting EurekaLog processing and handling into every thread would be risky and unnecessary. Normally, you should only enable EurekaLog for threads which you know. That is threads created by you, or threads which runs your code (such as threads from thread pool). You should not enable EurekaLog for arbitrary/unknown threads.
For this reason it is highly recommended to use manually controllable activation. You can use BeginThreadEx function instead of BeginThread function and use TThreadEx class instead of TThread class to create EurekaLog-enabled threads. If you can not control thread creation code (think of thread pools as example) - then you can use SetEurekaLogStateInThread function.
However, there still may be cases when you want to use "Default EurekaLog state in new threads" option:
Important Note: You can change "Default EurekaLog state in new threads" option for the above usage cases, but we recommend to use "Enabled for RTL threads, disabled for Windows threads" position when possible. Never turn "Default EurekaLog state in new threads" option into "Enabled" position until really needed.