Bug in 4.6.7

[Ludenka]

Hi Fabio, I've found a problem in EurekaLog 4, now 4.6.7. It's connected with safecall.
Scenario: I'm calling a BDE (borland database engine) function from a safecall method. The function fails raising an exception. And the problem is: The eurekalog exception dialog gets shown BEFORE the program returns from the failed bde function - it means, although I catch this exception outside of the
safecall function, the user gets the exception dialog on screen and must click "OK" to close it. I don't want to completely disable exceptions of this class, most of them are critical, I only want this particular one not to be displayed.
I've already sent example of this in an e-mail some weeks ago - without any usable solution as answer :(
Thanks for your help.

[admin]

I cannot find your email with the example.
Can you resend it to me please?

[Ludenka]

Message resent again - (I think the 3rd-4th time already - are you sure it doesn't fall in the spam bin? the domain name is @yahoo.com...)

[admin]

I have finally analysis your demo and it isn't an error but a standard behaviour for EurekaLog, because for every exception raised inside a SafeCall method EurekaLog show its dialog.

This because as default the safecall method are used into a client/server application, so if the exception is raised into an external process then EurekaLog must show the exception before pass it to the calling process (this to don't lose the original call stack), otherwise the calling process will show only its call stack loosing the original call stack that has caused the exception in the called process.

PS: excuse for the resend email problem but i had some problems with spam! :-)