Entry Level User

[SamH]

I am very pleased to have discovered EL. I have a huge D5 app that is quite a challenge. I notice that it takes up to 10 seconds for EL to respond to a forced bug in my app running remotely across the inet (running with LogMeIn).

1. Is there a setting the controls EL response time?
2. I got a ListArray violation on program close but no line number. Are there any settings that improve the possibility of getting back the line number?
3. I would like to insert my application logo in the EL popup. Is that part of the source code version?

Thanks
Sam

[Alex]

Hi.

Is there a setting the controls EL response time?
Can you describe what exactly do you mean by "response time"? I don't quite understand what your first question is, so can you explain it in more details, please?

Are there any settings that improve the possibility of getting back the line number?
Most common problems are disabled "Use Debug DCUs" option or using DLL/BPLs without debug information.
Please, see this article for more info: http://blog.eurekalog.com/?p=122

I would like to insert my application logo in the EL popup. Is that part of the source code version?
Well, this is not supported by EurekaLog out-of-the-box.
But, yes, if you have the Enterprise version (which comes with full sources) - then, of course, you may do whatever you want with it. Specifically, you may change dialogs in any way you want. Just note, that all error dialogs in EurekaLog are implemented in WinAPI (those are not VCL forms), so you may need a WinAPI-skills to change them.

[Kevin G. McCoy]

SamH wrote:

1. Is there a setting the controls EL response time?

EL is normally very fast.

I think what you are seeing is the lag when sending an error log either
via Email or through a web server.

I get the same thing in my apps, and there is nothing much you can do
about slow email servers or slow web sites. They will handshake your
email message or web login at their leisure. Your only recourse is to
use a faster email service or bug tracking web server - or maybe upgrade your internet connection.

In my application, to avoid having users think that my app had frozen up when EL is reporting a bug, I change the mouse cursor to an hourglass for the duration of the log file send.

Now the user is at least a little bit prepared for a few seconds of wait time. My users are used to the SQL hourglass cursor popping up for a couple seconds when my app is busy running database queries across the WAN, so EL logs don't disturb them much.

Note that I send a screen dump, the normal EL log, and two other non-EL logs in a Zip back to my Mantis bug-tracking web server. The Zip file can get pretty large and slow to send, especially on a low bandwidth Internet connection.

HTH,

Kevin G. McCoy