Separate Reports

[PizzaProgram]

Hi,
Sometimes I get a report with several thousands of lines, including more than just one report. (Which is fine!)
But,
it is very hard to scroll and find every 300-400 lines, where one ends and where the other starts.

Can you please add:
+4 Break lines, and
+1 '==========='... line (of 50 '=' signs) at the end of each report?

Before:

Code: Select all

008a6696       call    dword ptr [ecx+$dc]
008a669c       pop     esi
[...]

date/time          : 2022-11-29, 22:32:59, 249ms
computer name      : POMOPULT2017

After:

Code: Select all

008a6696       call    dword ptr [ecx+$dc]
008a669c       pop     esi
[...]




================================================
date/time          : 2022-11-29, 22:32:59, 249ms
computer name      : POMOPULT2017

Analysing a report to fix a problem is a time-sensitive thing.
(At some pizzerias in just 1 minute there can be up to:
+6 orders &
+30 new food entries &
+6 printing.
at the same time. Loosing 5 minutes can create a horrible chaos.)

[madshi]

You can use the "madExceptViewer" tool to look at such report files. Just start the tool and drag the file in. Or even better: If you use the file name extension "mbr" (madExcept bug report), double clicking the mbr file should automatically open the madExceptViewer tool on your development PC.

[PizzaProgram]

Yes, I know, Thank You very much!
But sadly that's not helping if you are not sitting at your PC, like trying to look at the emailed report on your phone, while the client is waiting in the line ...

At least a few empty lines would be nice to separate the reports please!
Last time I've just got one including 2000 lines of 5 month.
Not very easy to find where the last one begins.

(At some pizzerias 1 order gets handled in 10-20 seconds. So if solving a problem takes 5 minutes >> and the work stops that long >> that's already a chaos! )

[slemmnord]

Why not just search for the string "date/time"? It is first line in each report.
The few empty lines wont help you when there is so much text. It will still scroll by too fast to notice.
Also, you can add those lines already like this:
IMEException.BugReportSections.Add('hello', '========================');

[PizzaProgram]

Thank you for your answer!

Why not just search for the string "date/time"?

As I've tried to explain:
- every second counts and searching on a phone is difficult. (finding the "search" function, (if there is one) + typing the string ... )
- there are more lines of "date/time", hard to find the report date at first sight.

Also, you can add those lines already like this:
IMEException.BugReportSections.Add('hello', '========================');

This sound great! But where can I put this code?
- at the start of my app ?
- or is there some kind of global: OnReportBuildStart() event not documented in the HELP?
- Is that 'hello' section a special one, (which indicates the beginning of a report,) or just an example text?

[madshi]

You can use madExcept.RegisterExceptActionHandler and e.g. listen for the "eaSaveBugReport" event.