Custom Data in LogText

[tms]

Hello!
I cannot see Custom Data in LogText while it's present in .elf file and in
standard EL Error Window.
Also it's not present in EL Options, Log File tab (Show section).
I suggest adding soCustomData into TShowOptions also.
--
Regards
Tomski

[admin]

Hi,

tms wrote:
> Hello!
> I cannot see Custom Data in LogText while it's present in .elf file and in
> standard EL Error Window.

This because the first EurekaLog event (containing the LogText field) is called
before the OnCustomDataRequest event! :)

> Also it's not present in EL Options, Log File tab (Show section).
> I suggest adding soCustomData into TShowOptions also.
> --
> Regards
> Tomski

Good suggestion! :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[tms]

User "admin" wrote...
>> I cannot see Custom Data in LogText while it's present in .elf file and
>> in standard EL Error Window.
> This because the first EurekaLog event (containing the LogText field) is
> called before the OnCustomDataRequest event! :)

Hello!
Is it possible to fire this (OnCustomDataRequest) event before constructing
LogText?
If not, tell me where can I get complete LogText, please. Which other event?
May it be ExceptionActionNotify with atShowingExceptionInfo parameter?
--
Regards
Tomski

[admin]

tms wrote:
> User "admin" wrote...
>>> I cannot see Custom Data in LogText while it's present in .elf file and
>>> in standard EL Error Window.
>> This because the first EurekaLog event (containing the LogText field) is
>> called before the OnCustomDataRequest event! :)
>
> Hello!
> Is it possible to fire this (OnCustomDataRequest) event before constructing
> LogText?

No because the first event to call is always OnExceptionNotify, because with
this event it's possible choose if process the exception with EurekaLog or not.

> If not, tell me where can I get complete LogText, please. Which other event?
> May it be ExceptionActionNotify with atShowingExceptionInfo parameter?

Yes, it's so! :)

Example:



procedure TForm2.EurekaLog1ExceptionActionNotify(
EurekaExceptionRecord: TEurekaExceptionRecord;
EurekaAction: TEurekaActionType; var Execute: Boolean);
begin
if (EurekaAction = atShowingExceptionInfo) then
begin
MessageBox(0, PChar(EurekaExceptionRecord.LogText), '', 0);
end;
end;



> --
> Regards
> Tomski

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[tms]

It's not working for me. I use my own form for displaying error message
(from LogText) and I don't have edoShowExceptionDialog in
ExceptionDialogOptions...
So ExceptionActionNotify with atShowingExceptionInfo won't trigger. If I
won't select SaveLogFile also atSavingLogFile won't trigger. Same with
atSendingEmail. Maybe you could add something like atDoneExceptionProcessing
after all is showed, sent and saved (if checked in options). This action
notify would trigger always if Exception is processed by EurekaLog.
--
Regards
Tomski

User "admin"wrote...
> tms wrote:
>> User "admin" wrote...
>>>> I cannot see Custom Data in LogText while it's present in .elf file and
>>>> in standard EL Error Window.
>>> This because the first EurekaLog event (containing the LogText field) is
>>> called before the OnCustomDataRequest event! :)
>>
>> Hello!
>> Is it possible to fire this (OnCustomDataRequest) event before
>> constructing LogText?
>
> No because the first event to call is always OnExceptionNotify, because
> with this event it's possible choose if process the exception with
> EurekaLog or not.
>
>> If not, tell me where can I get complete LogText, please. Which other
>> event?
>> May it be ExceptionActionNotify with atShowingExceptionInfo parameter?
>
> Yes, it's so! :)
>

[admin]

Hi,

tms wrote:
> It's not working for me. I use my own form for displaying error message
> (from LogText) and I don't have edoShowExceptionDialog in
> ExceptionDialogOptions...
> So ExceptionActionNotify with atShowingExceptionInfo won't trigger. If I
> won't select SaveLogFile also atSavingLogFile won't trigger. Same with
> atSendingEmail. Maybe you could add something like atDoneExceptionProcessing
> after all is showed, sent and saved (if checked in options). This action
> notify would trigger always if Exception is processed by EurekaLog.
> --
> Regards
> Tomski
>
> [...]

I think the best solution is show your custom Form in the
OnExceptionActionNotify event just in for the atShowingExceptionInfo action,
setting the Execute parameter to false. :)

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[tms]

May be... may be... I haven't tried that way :) Thanks!
--
Regards
Tomski

User "admin"wrote...
> I think the best solution is show your custom Form in the
> OnExceptionActionNotify event just in for the atShowingExceptionInfo
> action, setting the Execute parameter to false. :)
>
> --
> Best regards...
>
> Fabio Dell'Aria.

[admin]

Hi,

tms wrote:
> May be... may be... I haven't tried that way :) Thanks!
> --
> Regards
> Tomski

You're welcome! :)

> User "admin"wrote...
>> I think the best solution is show your custom Form in the
>> OnExceptionActionNotify event just in for the atShowingExceptionInfo
>> action, setting the Execute parameter to false. :)
>>
>> --
>> Best regards...
>>
>> Fabio Dell'Aria.

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!

[tms]

User "admin" wrote...
>>> I think the best solution is show your custom Form in the
>>> OnExceptionActionNotify event just in for the atShowingExceptionInfo
>>> action, setting the Execute parameter to false. :)

All works fine that way except Custom Data text. When I set CustomData
(OnCustomDataRequest) with some string including ": ", Custom Data section
in LogText shows it as ":_". Also if CustomData begins with CRLF, LogText
adds "." before it.

Example:
OnCustomDataRequest:
CustomData := #13#10'Driver: SQL Server'

EurekaExceptionRecord.LogText (Section 7.1):
'7.1 : .'#13#10'Driver:_SQL Server'

--
Regards
Tomski

[admin]

Hi,

this is required to can parser the .elf file (is required from the .ELF file format rules).